Techniques for transmitting a physical uplink shared channel in an uplink pilot time slot

ABSTRACT

Techniques for wireless communication are described. A method for wireless communication at a user equipment (UE) includes identifying a physical uplink shared channel (PUSCH) to transmit in an uplink pilot time slot (UpPTS) of a subframe, determining whether to transmit uplink control information (UCI) on the PUSCH in the UpPTS, and transmitting the PUSCH in the UpPTS based at least in part on the determining. A method for wireless communication at a network access device includes determining whether to schedule a transmission of UCI on a PUSCH in a UpPTS of a subframe, scheduling the PUSCH in the UpPTS based at least in part on the determining, and transmitting, to a UE, scheduling information for the PUSCH in the UpPTS.

CROSS REFERENCES

The present Application is a Continuation of U.S. patent applicationSer. No. 15/462,356 by Chen, et al., entitled “Techniques ForTransmitting A Physical Uplink Shared Channel In An Uplink Pilot TimeSlot” filed Mar. 17, 2017, which claims priority to U.S. ProvisionalPatent Application No. 62/357,843 by CHEN, et al., entitled “Techniquesfor Transmitting A Physical Uplink Shared Channel In An Uplink PilotTime Slot,” filed Jul. 1, 2016 and to U.S. Provisional PatentApplication No 62/372,642 by CHEN, et al., entitled “Techniques forTransmitting A Physical Uplink Shared Channel In An Uplink Pilot TimeSlot,” filed Aug. 9, 2016, assigned to the assignee hereof.

BACKGROUND Field of the Disclosure

The present disclosure, for example, relates to wireless communicationsystems, and more particularly to techniques for transmitting a physicaluplink shared channel (PUSCH) in an uplink pilot time slot (UpPTS) suchas a six symbol period UpPTS.

Description of Related Art

Wireless communication systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be multiple-accesssystems capable of supporting communication with multiple users bysharing the available system resources (e.g., time, frequency, andpower). Examples of such multiple-access systems include code-divisionmultiple access (CDMA) systems, time-division multiple access (TDMA)systems, frequency-division multiple access (FDMA) systems, andorthogonal frequency-division multiple access (OFDMA) systems.

By way of example, a wireless multiple-access communication system mayinclude a number of network access devices (e.g., base stations), eachsimultaneously supporting communication for multiple communicationdevices, otherwise known as user equipment (UEs). A base station maycommunicate with UEs on downlink channels (e.g., downlinks, fortransmissions from a base station to a UE) and uplink channels (e.g.,uplinks, for transmissions from a UE to a base station).

Some wireless communication systems may provide a UpPTS during a portionof a subframe. A UE may transmit pilot signals (or reference signals) toa base station during a UpPTS.

SUMMARY

In some Long Term Evolution (LTE) and LTE-Advanced (LTE-A) networks, atwo symbol period uplink pilot time slot (UpPTS) is provided in somesubframes of some configurations of a time domain duplexing (TDD) radioframe structure. The two symbol period UpPTS may be used by userequipment (UEs) to transmit pilot signals (or reference signals) to abase station. The two symbol period UpPTS may also be used by UEsperforming random access procedures. In some LTE/LTE-A networks, a sixsymbol period UpPTS may be provided in some subframes of someconfigurations of a TDD radio frame structure. The present disclosuredescribes techniques for transmitting a physical uplink shared channel(PUSCH) in a UpPTS.

In one example, a method for wireless communication at a UE isdescribed. The method may include identifying a PUSCH to transmit in aUpPTS of a subframe, determining whether to transmit uplink controlinformation (UCI) on the PUSCH in the UpPTS, and transmitting the PUSCHin the UpPTS based at least in part on the determining.

In one example, an apparatus for wireless communication at a UE isdescribed. The apparatus may include means for identifying a PUSCH totransmit in a UpPTS of a subframe, means for determining whether totransmit UCI on the PUSCH in the UpPTS, and means for transmitting thePUSCH in the UpPTS based at least in part on the determining.

In one example, another apparatus for wireless communication at a UE isdescribed. The apparatus may include a processor, and memory inelectronic communication with the processor. The processor and thememory may be configured to identify a PUSCH to transmit in a UpPTS of asubframe, determine whether to transmit UCI on the PUSCH in the UpPTS,and transmit the PUSCH in the UpPTS based at least in part on thedetermining.

In one example, a non-transitory computer-readable medium storingcomputer-executable code for wireless communication at a UE isdescribed. The code may be executable by a processor to identify a PUSCHto transmit in a UpPTS of a subframe, determine whether to transmit UCIon the PUSCH in the UpPTS, and transmit the PUSCH in the UpPTS based atleast in part on the determining.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for receiving, during atransmission time interval (TTI), scheduling information for the PUSCHin the UpPTS. A timing of the TTI may be based at least in part on alatency reduction capability of the UE. In some examples of the method,apparatus, and non-transitory computer-readable medium described above,the latency reduction capability of the UE may include at least one of:a scheduling timing reduction capability, a TTI duration reductioncapability, or a combination thereof. In some examples of the method,apparatus, and non-transitory computer-readable medium described above,the timing of the TTI in which the scheduling information is receivedmay include: a leading boundary occurring at least two subframes priorto the UpPTS, or a leading boundary occurring at least 2.5 subframesprior to the UpPTS.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for at least one of: separatelymanaging uplink hybrid automatic repeat request (HARQ) for the PUSCH inthe UpPTS and uplink HARQ for PUSCH transmissions in uplink TTIs,jointly managing the uplink HARQ for the PUSCH in the UpPTS and theuplink HARQ for PUSCH transmissions in uplink TTIs, receiving the uplinkHARQ for the PUSCH in the UpPTS and the uplink HARQ for PUSCHtransmissions in uplink TTIs asynchronously, or receiving anacknowledgement of the PUSCH in the UpPTS in a same set of physical HARQindicator channel (PHICH) resources used to acknowledge PUSCHtransmissions in uplink subframes.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for determining whether an uplinkTTI is scheduled to be transmitted on at least a first component carrier(CC) while the PUSCH in the UpPTS is transmitted on a second CC. Thedetermining whether to transmit UCI on the PUSCH may be based at leastin part on whether the uplink TTI is scheduled to be transmitted on atleast the first CC.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for determining the PUSCH in theUpPTS is scheduled to be transmitted when operating in a carrieraggregation mode, and determining, based at least in part on thedetermining the PUSCH in the UpPTS is scheduled to be transmitted whenoperating in the carrier aggregation mode, to not transmit at least oneof: periodic channel state information (P-CSI) on the PUSCH in theUpPTS, aperiodic channel state information (A-C SI) on the PUSCH in theUpPTS, UCI on the PUSCH in the UpPTS, or a combination thereof.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for determining the PUSCH in theUpPTS is scheduled to be transmitted when operating in a carrieraggregation mode, and determining to transmit, in parallel with thePUSCH in the UpPTS, on a CC that does not carry the PUSCH in the UpPTS,and based at least in part on the determining the PUSCH in the UpPTS isscheduled to be transmitted when operating in the carrier aggregationmode, at least one of: P-CSI, A-CSI, UCI, or a combination thereof.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for determining the PUSCH in theUpPTS is scheduled to be transmitted when operating in a carrieraggregation mode, and selecting a CC for transmitting UCI based at leastin part on a prioritization of CCs that biases CC selection away from aCC carrying the PUSCH in the UpPTS.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for determining whether the UE isconfigured for parallel physical uplink control channel (PUCCH) andPUSCH transmission, and determining whether to transmit UCI on the PUSCHbased at least in part on whether the UE is configured for parallelPUCCH and PUSCH transmission.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for receiving downlink controlinformation (DCI), and identifying an uplink grant for the PUSCH in theUpPTS, received in the DCI, based at least in part on: a state of aninformation field included in the DCI, a masking of a control channelincluding the DCI with a predetermined cyclic redundancy check (CRC)mask, an association of the uplink grant with a predetermined decodingcandidate, a size of the DCI, an identifier of a subframe in which theDCI is received, a DCI format, or a combination thereof.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for receiving DCI, determining asize of the DCI, and identifying, within the DCI, at least one decodingcandidate for an uplink grant for the PUSCH in the UpPTS, the at leastone decoding candidate based at least in part on the size of the DCI.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for identifying a first powercontrol parameter for a TTI, and determining a second power controlparameter for the PUSCH in the UpPTS based at least in part on the firstpower control parameter for the TTI. In some examples of the method,apparatus, and non-transitory computer-readable medium described above,the second power control parameter may be determined based at least inpart on: a semi-static relationship between the first power controlparameter and the second control parameter, or a variable structure ofthe PUSCH in the UpPTS.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for receiving schedulinginformation for the PUSCH in the UpPTS, in which the schedulinginformation includes a first offset that differs from a second offsetfor at least one UCI type configuration received for an uplink subframe.

Some examples of the method, apparatus, and computer-readable mediumdescribed above may further include processes, features, means,instructions, or code for determining, based at least in part on anumber of reference symbols to be transmitted in the UpPTS, whether toenable at least one of: frequency hopping during transmission of thePUSCH in the UpPTS, use of an orthogonal cover code (OCC) duringtransmission of the PUSCH in the UpPTS, or a combination thereof.

Some examples of the method, apparatus, and computer-readable mediumdescribed above may further include processes, features, means,instructions, or code for transmitting a random access preamble, andreceiving, in response to transmitting the random access preamble, arandom access response message scheduling the PUSCH in the UpPTS.

Some examples of the method, apparatus, and computer-readable mediumdescribed above may further include processes, features, means,instructions, or code for transmitting a demodulation reference signal(DM-RS) for the PUSCH in the UpPTS based at least in part on a DM-RSpattern that differs from a DM-RS pattern used for a PUSCH in an uplinksubframe.

In one example, a method for wireless communication at a network accessdevice is described. The method may include determining whether toschedule a transmission of UCI on a PUSCH in a UpPTS of a subframe,scheduling the PUSCH in the UpPTS based at least in part on thedetermining, and transmitting, to a UE, scheduling information for thePUSCH in the UpPTS.

In one example, an apparatus for wireless communication at a networkaccess device is described. The apparatus may include means fordetermining whether to schedule a transmission of UCI on a PUSCH in aUpPTS of a subframe, means for scheduling the PUSCH in the UpPTS basedat least in part on the determining, and means for transmitting, to aUE, scheduling information for the PUSCH in the UpPTS.

In one example, another apparatus for wireless communication at anetwork access device is described. The apparatus may include aprocessor, and memory in electronic communication with the processor.The processor and the memory may be configured to determine whether toschedule a transmission of UCI on a PUSCH in a UpPTS of a subframe,schedule the PUSCH in the UpPTS based at least in part on thedetermining, and transmit, to a UE, scheduling information for the PUSCHin the UpPTS.

In one example, a non-transitory computer-readable medium storingcomputer-executable code for wireless communication at a network accessdevice is described. The code may be executable by a processor todetermine whether to schedule a transmission of UCI on a PUSCH in aUpPTS of a subframe, schedule the PUSCH in the UpPTS based at least inpart on the determining, and transmit, to a UE, scheduling informationfor the PUSCH in the UpPTS.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for selecting a timing of a TTIin which the scheduling information is transmitted based at least inpart on a latency reduction capability of the UE. In some examples ofthe method, apparatus, and non-transitory computer-readable mediumdescribed above, the latency reduction capability of the UE may includeat least one of: a scheduling timing reduction capability, a TTIduration reduction capability, or a combination thereof. In someexamples of the method, apparatus, and non-transitory computer-readablemedium described above, the timing of the TTI in which the schedulinginformation is transmitted may include: a leading boundary occurring atleast two subframes prior to the UpPTS, or a leading boundary occurringat least 2.5 subframes prior to the UpPTS.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for at least one of: separatelymanaging uplink HARQ for the PUSCH in the UpPTS and uplink HARQ forPUSCH transmissions in uplink TTIs, jointly managing the uplink HARQ forthe PUSCH in the UpPTS and the uplink HARQ for PUSCH transmissions inuplink TTIs, transmitting the uplink HARQ for the PUSCH in the UpPTS andthe uplink HARQ for PUSCH transmissions in uplink TTIs asynchronously,or transmitting an acknowledgement of the PUSCH in the UpPTS in a sameset of PHICH resources used to acknowledge PUSCH transmissions in uplinksubframes.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for transmitting DCI to the UE,and indicating a presence of an uplink grant for the PUSCH in the UpPTS,in the DCI, based at least in part on: a state of an information fieldincluded in the DCI, a masking of a control channel including the DCIwith a predetermined CRC mask, an association of the uplink grant with apredetermined decoding candidate, a size of the DCI, an identifier of asubframe in which the DCI is received, a DCI format, or a combinationthereof.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for selecting a first offset forthe scheduling information, in which the first offset differs from asecond offset for at least one UCI type configuration selected for anuplink subframe, and indicating the first offset in the schedulinginformation.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for receiving a random accesspreamble, and scheduling the PUSCH in the UpPTS in response to receivingthe random access preamble.

Some examples of the method, apparatus, and non-transitorycomputer-readable medium described above may further include processes,features, means, instructions, or code for receiving a DM-RS for thePUSCH in the UpPTS based at least in part on a DM-RS pattern thatdiffers from a DM-RS pattern used for a PUSCH in an uplink subframe.

The foregoing has outlined rather broadly the techniques and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionaltechniques and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the scope of the appended claims. Characteristics of theconcepts disclosed herein, both their organization and method ofoperation, together with associated advantages will be better understoodfrom the following description when considered in connection with theaccompanying figures. Each of the figures is provided for the purpose ofillustration and description, and not as a definition of the limits ofthe claims.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of the presentdisclosure may be realized by reference to the following drawings. Inthe appended figures, similar components or functions may have the samereference label. Further, various components of the same type may bedistinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

FIG. 1 illustrates an example of a wireless communication system, inaccordance with various aspects of the present disclosure;

FIG. 2 shows a set of time domain duplexing (TDD) radio frame structuresthat may be supported by the wireless communication devices (e.g., basestations and user equipment (UEs)) of a wireless communication system,in accordance with various aspects of the present disclosure;

FIG. 3 shows a TDD radio frame structure having a downlink-uplink(DL-UL) subframe configuration associated with a 5 ms switch-pointperiodicity, in accordance with various aspects of the presentdisclosure;

FIG. 4 shows a TDD radio frame structure having a DL-UL subframeconfiguration associated with a 5 ms switch-point periodicity, inaccordance with various aspects of the present disclosure;

FIG. 5 shows a configuration of a subframe including multiple parallelcomponent carriers (CCs), in accordance with various aspects of thepresent disclosure;

FIG. 6 shows alternative configurations of a subframe including a sixsymbol period uplink pilot time slot (UpPTS), in accordance with variousaspects of the present disclosure;

FIG. 7 shows a block diagram of an apparatus for use in wirelesscommunication, in accordance with various aspects of the presentdisclosure;

FIG. 8 shows a block diagram of a wireless communication manager for usein wireless communication, in accordance with various aspects of thepresent disclosure;

FIG. 9 shows a block diagram of an apparatus for use in wirelesscommunication, in accordance with various aspects of the presentdisclosure;

FIG. 10 shows a block diagram of a wireless communication manager foruse in wireless communication, in accordance with various aspects of thepresent disclosure;

FIG. 11 shows a block diagram of a UE for use in wireless communication,in accordance with various aspects of the present disclosure;

FIG. 12 shows a block diagram of a base station (e.g., a base stationforming part or all of an eNB) for use in wireless communication, inaccordance with various aspects of the present disclosure;

FIG. 13 is a flow chart illustrating an example of a method for wirelesscommunication at a UE, in accordance with various aspects of the presentdisclosure;

FIG. 14 is a flow chart illustrating an example of a method for wirelesscommunication at a UE, in accordance with various aspects of the presentdisclosure;

FIG. 15 is a flow chart illustrating an example of a method for wirelesscommunication at a network access device (e.g., a base station), inaccordance with various aspects of the present disclosure; and

FIG. 16 is a flow chart illustrating an example of a method for wirelesscommunication at a network access device (e.g., a base station), inaccordance with various aspects of the present disclosure.

DETAILED DESCRIPTION

Techniques are described in which an uplink pilot time slot (UpPTS),such as a six symbol period UpPTS, is used by user equipment (UEs) totransmit a physical uplink shared channel PUSCH. Some techniques aredirected to the selection of a timing (e.g., the selection of a subframeor other transmission time interval (TTI)) for transmitting/receivingscheduling information for a PUSCH transmitted in a UpPTS. In someexamples, the selection of a timing for transmitting/receivingscheduling information for a PUSCH in a UpPTS may be based at least inpart on a capability of a UE. Some techniques are directed todetermining whether to transmit uplink control information (UCI) on aPUSCH in a UpPTS. In some examples, a determination of whether totransmit UCI on a PUSCH in a UpPTS may be based at least in part onwhether a UE is operating in a carrier aggregation mode. Some techniquesare directed to differentiating an uplink grant for a PUSCH in a UpPTSfrom uplink grants for other uplink transmissions, such as an uplinktransmission in an immediate next uplink TTI following a PUSCH in aUpPTS.

The following description provides examples, and is not limiting of thescope, applicability, or examples set forth in the claims. Changes maybe made in the function and arrangement of elements discussed withoutdeparting from the scope of the disclosure. Various examples may omit,substitute, or add various procedures or components as appropriate. Forinstance, the operations of the described methods may be performed in anorder different from that described, and various operations may beadded, omitted, or combined. Also, features described with respect tosome examples may be combined in other examples.

FIG. 1 illustrates an example of a wireless communication system 100, inaccordance with various aspects of the present disclosure. The wirelesscommunication system 100 may include network access devices (e.g., basestations 105), UEs 115, and a core network 130. The core network 130 mayprovide user authentication, access authorization, tracking, InternetProtocol (IP) connectivity, and other access, routing, or mobilityfunctions. The base stations 105 may interface with the core network 130through backhaul links 132 (e.g., S1, etc.) and may perform radioconfiguration and scheduling for communication with the UEs 115, or mayoperate under the control of a base station controller (not shown). Invarious examples, the base stations 105 may communicate, either directlyor indirectly (e.g., through core network 130), with each other overbackhaul links 134 (e.g., X1, etc.), which may be wired or wirelesscommunication links.

The base stations 105 may wirelessly communicate with the UEs 115 viaone or more base station antennas. Each of the base station 105 sitesmay provide communication coverage for a respective geographic coveragearea 110. In some examples, a base station 105 may be referred to as abase transceiver station, a radio base station, an access point, a radiotransceiver, a NodeB, an eNodeB (eNB), a Home NodeB, a Home eNodeB, orsome other suitable terminology. The geographic coverage area 110 for abase station 105 may be divided into sectors making up a portion of thecoverage area (not shown). The wireless communication system 100 mayinclude base stations 105 of different types (e.g., macro or small cellbase stations). There may be overlapping geographic coverage areas 110for different technologies.

In some examples, the wireless communication system 100 may include anLTE/LTE-A network. In LTE/LTE-A networks, the term evolved Node B (eNB)may be used to describe the base stations 105, while the term UE may beused to describe the UEs 115. The wireless communication system 100 maybe a Heterogeneous LTE/LTE-A network in which different types of eNBsprovide coverage for various geographical regions. For example, each eNBor base station 105 may provide communication coverage for a macro cell,a small cell, or other types of cell. The term “cell” is a 3GPP termthat can be used to describe a base station, a carrier or componentcarrier associated with a base station, or a coverage area (e.g.,sector, etc.) of a carrier or base station, depending on context.

A macro cell may cover a relatively large geographic area (e.g., severalkilometers in radius) and may allow unrestricted access by UEs withservice subscriptions with the network provider. A small cell may be alower-powered base station, as compared with a macro cell that mayoperate in the same or different (e.g., licensed, shared, etc.) radiofrequency spectrum bands as macro cells. Small cells may include picocells, femto cells, and micro cells according to various examples. Apico cell may cover a relatively smaller geographic area and may allowunrestricted access by UEs with service subscriptions with the networkprovider. A femto cell may additionally or alternatively cover arelatively small geographic area (e.g., a home) and may providerestricted access by UEs having an association with the femto cell(e.g., UEs in a closed subscriber group (CSG), UEs for users in thehome, and the like). An eNB for a macro cell may be referred to as amacro eNB. An eNB for a small cell may be referred to as a small celleNB, a pico eNB, a femto eNB or a home eNB. An eNB may support one ormultiple (e.g., two, three, four, and the like) cells (e.g., componentcarriers).

The wireless communication system 100 may support synchronous orasynchronous operation. For synchronous operation, the base stations mayhave similar frame timing, and transmissions from different basestations may be approximately aligned in time. For asynchronousoperation, the base stations may have different frame timing, andtransmissions from different base stations may not be aligned in time.The techniques described herein may be used for either synchronous orasynchronous operations.

The communication networks that may accommodate some of the variousdisclosed examples may be packet-based networks that operate accordingto a layered protocol stack. In the user plane, communications at thebearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based.A Radio Link Control (RLC) layer may perform packet segmentation andreassembly to communicate over logical channels. A Medium Access Control(MAC) layer may perform priority handling and multiplexing of logicalchannels into transport channels. The MAC layer may additionally oralternatively use Hybrid ARQ (HARD) to provide retransmission at the MAClayer to improve link efficiency. In the control plane, the RadioResource Control (RRC) protocol layer may provide establishment,configuration, and maintenance of an RRC connection between a UE 115 andthe base stations 105 or core network 130 supporting radio bearers forthe user plane data. At the Physical (PHY) layer, the transport channelsmay be mapped to Physical channels.

The UEs 115 may be dispersed throughout the wireless communicationsystem 100, and each UE 115 may be stationary or mobile. A UE 115 mayalso include or be referred to by those skilled in the art as a mobilestation, a subscriber station, a mobile unit, a subscriber unit, awireless unit, a remote unit, a mobile device, a wireless device, awireless communication device, a remote device, a mobile subscriberstation, an access terminal, a mobile terminal, a wireless terminal, aremote terminal, a handset, a user agent, a mobile client, a client, orsome other suitable terminology. A UE 115 may be a cellular phone, apersonal digital assistant (PDA), a wireless modem, a wirelesscommunication device, a handheld device, a tablet computer, a laptopcomputer, a cordless phone, a wireless local loop (WLL) station, or thelike. A UE may be able to communicate with various types of basestations and network equipment, including macro eNBs, small cell eNBs,relay base stations, and the like.

The communication links 125 shown in wireless communication system 100may include downlinks (DLs), from a base station 105 to a UE 115, oruplinks (ULs), from a UE 115 to a base station 105. The downlinks mayalso be called forward links, while the uplinks may also be calledreverse links.

In some examples, each communication link 125 may include one or morecarriers, where each carrier may be a signal made up of multiplesub-carriers (e.g., waveform signals of different frequencies) modulatedaccording to the various radio technologies described above. Eachmodulated signal may be transmitted on a different sub-carrier and maycarry control information (e.g., reference signals, control channels,etc.), overhead information, user data, etc. The communication links 125may transmit bidirectional communications using a frequency domainduplexing (FDD) operation (e.g., using paired spectrum resources) or aTDD operation (e.g., using unpaired spectrum resources). Framestructures for FDD operation (e.g., frame structure type 1) and TDDoperation (e.g., frame structure type 2) may be defined.

In some examples of the wireless communication system 100, base stations105 or UEs 115 may include multiple antennas for employing antennadiversity schemes to improve communication quality and reliabilitybetween base stations 105 and UEs 115. Additionally or alternatively,base stations 105 or UEs 115 may employ multiple-input, multiple-output(MIMO) techniques that may take advantage of multi-path environments totransmit multiple spatial layers carrying the same or different codeddata.

The wireless communication system 100 may support operation on multiplecells or carriers, a feature which may be referred to as carrieraggregation (CA) or dual-connectivity operation. A carrier may also bereferred to as a component carrier (CC), a layer, a channel, etc. Theterms “carrier,” “component carrier,” “cell,” and “channel” may be usedinterchangeably herein. Carrier aggregation may be used with both FDDand TDD component carriers.

In an LTE/LTE-A network, a UE 115 may be configured to communicate usingup to five CCs when operating in a carrier aggregation mode ordual-connectivity mode. One or more of the CCs may be configured as a DLCC, and one or more of the CCs may be configured as a UL CC. Also, oneof the CCs allocated to a UE 115 may be configured as a primary CC(PCC), and the remaining CCs allocated to the UE 115 may be configuredas secondary CCs (SCCs).

FIG. 2 shows a set of TDD radio frame structures 200 that may besupported by the wireless communication devices (e.g., base stations andUEs) of a wireless communication system, in accordance with variousaspects of the present disclosure. In some examples, the wirelesscommunication system may be an example of aspects of the wirelesscommunication system 100 described with reference to FIG. 1.

In some examples, the TDD radio frame structures may include sets ofsubframes (e.g., ten subframes, numbered 0-9) configured in accordancewith different TDD DL-UL subframe configurations (e.g., 7 different TDDDL-UL subframe configurations, numbered 0-6). In some examples, the TDDDL-UL subframe configurations may include subsets of DL-UL UL subframeconfigurations associated with different switch-point periodicities. Forexample, a first subset of DL-UL subframe configurations may beassociated with a 5 millisecond (ms) switch-point periodicity, and asecond subset of DL-UL subframe configurations may be associated with a10 ms switch-point periodicity. Each DL-UL subframe configuration in thefirst subset of DL-UL subframe configurations may include a number ofdownlink (D) subframes, a number of uplink (U) subframes, and twospecial (S) subframes. Each DL-UL subframe configuration in the secondsubset of DL-UL subframe configurations may include a number of Dsubframes, a number of U subframes, and one S subframe. Each S subframemay provide a transition between a downlink burst (e.g., one or more Dsubframes) and an uplink burst (e.g., one or more U subframes).

FIG. 3 shows a TDD radio frame structure 300 having a DL-UL subframeconfiguration associated with a 5 ms switch-point periodicity, inaccordance with various aspects of the present disclosure. In someexamples, the DL-UL subframe configuration may be an example of aspectsof the DL-UL subframe configuration numbered 0, 1, 2, or 6 in FIG. 2.

In some examples, the TDD radio frame structure 300 may include a firsthalf-frame structure 305 followed by a second half-frame structure 310.Each of the first half-frame structure 305 and the second half-framestructure 310 may have a duration equal to half the duration of the TDDradio frame structure 300. In some examples, each of the firsthalf-frame structure 305 and the second half-frame structure 310 mayhave the same structure and may include a subset of five subframes 315(e.g., subframes 315 numbered 0, 1, 2, 3, and 4, or subframes 315numbered 5, 6, 7, 8, and 9).

In some examples, each of the subframes 315 configured as a downlinksubframe or an uplink subframe (e.g., subframes (SFs) 315 numbered 0, 2,3, 4, 5, 7, 8, and 9) may include a first slot 320 followed by a secondslot 325. Each of the first slot 320 and the second slot 325 may have aslot duration equal to half the duration of a subframe. In someexamples, each of the subframes 315 configured as a special subframe(e.g., subframes 315 numbered 2 and 6) may include a downlink pilot timeslot (DwPTS) 330, a guard period (GP) 335, and an uplink pilot time slot(UpPTS) 340, wherein the guard period can provide for a transition gapfrom downlink to uplink in the TDD mode.

In some wireless communications systems, it may be possible todynamically adapt the DL-UL subframe configuration used by the wirelesscommunication system (or a subset of devices (e.g., base stations andUEs) of the wireless communication system) based at least in part on theDL-UL traffic needs of the wireless communication system. A wirelesscommunication system employing evolved interference management fortraffic adaptation (eIMTA) may perform such an adaptation. For example,if a large data burst on a downlink is needed for a short duration, theTDD radio frame structure used for communication between a subset ofwireless communication devices in a wireless communication system may bechanged from the DL-UL subframe configuration numbered 1 in FIG. 2 (witha 6:4 DL:UL ratio) to the DL-UL subframe configuration numbered 5 inFIG. 2 (with a 9:1 DL:UL ratio). In some examples, the DL-UL subframeconfiguration employed for communication may be adapted no slower than640 ms, and as fast as 10 ms.

The use of different DL-UL subframe configurations by different cellsmay in some cases result in inter-cell interference. For example,inter-cell interference may result from a first cell employing a firstDL-UL subframe configuration including a D subframe in a subframe numbern, and a second cell employing a second DL-UL subframe configurationincluding a U subframe in the subframe number n.

In some examples, a base station may provide a dynamic indication of theDL-UL subframe configuration employed. The dynamic indication may beprovided by explicit layer signaling of a reconfiguration in aUE-group-common physical downlink control channel (PDCCH) or enhancedPDCCH (EPDCCH).

The adaptation of DL-UL subframe configurations based at least in parton traffic needs may increase the complexity of HARQ management. In someexamples, HARQ management may be simplified by identifying one or morereference DL-UL subframe configurations for HARQ. For example, for ULHARQ, scheduling and HARQ timing may be based on a DL-UL subframeconfiguration indicated in a system information block (SIB) (e.g., aDL-UL subframe configuration indicated in a SIB1). For DL HARQ,scheduling and HARQ timing may be based on a reference DL-UL subframeconfiguration indicated for use by a UE (e.g., the DL-UL subframeconfiguration numbered 2, 4, or 5 in FIG. 2).

In wireless communication systems employing eIMTA, some subframes (e.g.,some subframe numbers) may be subject to dynamic adaptation intransmission direction, while other subframes may not be subject todynamic adaptation in transmission direction. For example, D subframesin a DL-UL subframe configuration indicated in a SIB1 may not be subjectto dynamic adaptation in transmission direction, and U subframes in aDL-UL subframe configuration indicated for use by a UE for DL HARQ maynot be subject to dynamic adaptation in transmission direction.

The UpPTS 340 described with reference to FIG. 3 may have differentdurations. In some examples, the UpPTS 340 may have a duration of one ortwo symbols (e.g., one or two orthogonal frequency-division multiplexing(OFDM) symbol periods or single-carrier frequency division multiplexing(SC-FDM) symbol periods). In these examples, the UpPTS 340 may be usedto carry a shortened physical random access channel (PRACH) (e.g., aLTE/LTE-A PRACH format 4) and/or a sounding reference signal (SRS), butno physical uplink control channel (PUCCH) transmission or physicaluplink shared channel (PUSCH) transmission. In other examples, the UpPTS340 may have a longer duration (e.g., a six symbol period (e.g., sixsymbol period) duration). In these examples, the UpPTS 340 may providemore SRS transmission opportunities (e.g., for 3D-MIMO applications) orbe used to carry a PUSCH transmission.

In some examples, a PUSCH to be transmitted in a UpPTS (i.e., a PUSCH ina UpPTS) may be separately scheduled from a UL transmission in animmediate next UL subframe. Scheduling a PUSCH in a UpPTS separatelyfrom other UL transmissions can provide greater scheduling flexibility.In some examples, however, the timing of a transmission of schedulinginformation for a PUSCH in a UpPTS may be tied to the timing of atransmission of scheduling information for a UL transmission in animmediate next UL subframe (e.g., both sets of scheduling informationmay be transmitted during a same TTI or on a same channel). Thetransmission of scheduling information for both a PUSCH in a UpPTS and aUL transmission in an immediate next UL subframe, in a same TTI, mayreduce a UE's lead time for preparing to transmit the PUSCH in the UpPTS(e.g., in a radio frame structure based on 1 ms subframes (or 1 msTTIs), the UE's lead time for preparing to transmit the PUSCH in theUpPTS may be reduced by 0.5 ms when the duration of the PUSCH in theUpPTS is 0.5 ms).

When a UpPTS in which a PUSCH is transmitted has a duration that is lessthan a first duration of a first TTI associated with a first radio framestructure (e.g., less than a duration of a LTE/LTE-A subframe), and lessthan a second duration of a second TTI associated with a second radioframe structure (e.g., less than a duration of an ultra low latency(ULL) TTI, or less than a duration of a slot of a LTE/LTE-A subframe),the timing of a transmission of scheduling information for the PUSCH inthe UpPTS may vary depending on a UE's capability to operate inaccordance with the first radio frame structure or the second radioframe structure. The timing of the transmission of schedulinginformation for the PUSCH in the UpPTS may also vary depending on a UE'sprocessing capabilities. In some examples, the timing of a TTI in whichthe scheduling information for the PUSCH in the UpPTS is transmitted orreceived (e.g., the timing of a leading boundary of the TTI) may bebased at least in part on a latency reduction capability of the UE. Alatency reduction capability may include, for example, at least one of ascheduling timing reduction capability, a TTI duration reductioncapability, or a combination thereof.

FIG. 4 shows a TDD radio frame structure 400 having a DL-UL subframeconfiguration associated with a 5 ms switch-point periodicity, inaccordance with various aspects of the present disclosure. In someexamples, the DL-UL subframe configuration may be an example of aspectsof the DL-UL subframe configuration numbered 2 in FIG. 2. As shown, theDL-UL subframe configuration may include D subframes, U subframes, and Ssubframes. An uplink transmission (e.g., a PUSCH) may be scheduled fortransmission in a UpPTS (e.g., a six symbol period UpPTS) of each Ssubframe.

An uplink transmission (e.g., a PUSCH) in each of the U subframes may bescheduled, at least in part, based on an uplink grant transmitted in anearlier-transmitted D subframe. A PUSCH in a six symbol period UpPTS ineach of the S subframes may also be scheduled, at least in part, basedon an uplink grant transmitted in an earlier-transmitted subframe.

For a LTE/LTE-A UE that is not capable of latency reduction (e.g., a UEthat does not have a latency reduction capability, a UE that does nothave a ULL latency reduction capability, and/or a UE that is associatedwith a n+4 scheduling timing in which scheduling information for ULsubframes is transmitted four subframes before a UL SF n), schedulinginformation for the PUSCH in the UpPTS in SF 6 may betransmitted/received during SF 3, such that the scheduling informationfor the PUSCH in the UpPTS is transmitted/received in a TTI having aleading boundary occurring at least 3.5 subframes prior to the UpPTS inSF 6. Scheduling information for a UL transmission in the immediate nextUL subframe following the UpPTS (i.e., SF 7) may also betransmitted/received during SF 3, such that the scheduling informationfor the UL transmission in the immediate next UL subframe following theUpPTS is transmitted/received in a TTI having a leading boundaryoccurring at least four subframes prior to SF 7. In some examples, thescheduling information for the PUSCH in the UpPTS may be transmitted ina PDCCH but not an EPDCCH in SF 3, to provide the LTE/LTE-A UE enoughtime to decode and process the scheduling information for the PUSCH inthe UpPTS.

For a LTE/LTE-A UE that is capable of latency reduction (e.g., a UE thathas a scheduling time reduction capability, such as a n+3 schedulingtiming reduction capability in which scheduling information for ULsubframes is transmitted three subframes before a UL SF n), schedulinginformation for the PUSCH in the UpPTS in SF 6 may betransmitted/received during SF 4, such that the scheduling informationfor the PUSCH in the UpPTS is transmitted/received in a TTI having aleading boundary occurring at least 2.5 subframes prior to the UpPTS inSF 6. In some examples, scheduling information for a UL transmission inthe immediate next UL subframe following the UpPTS (i.e., SF 7) may alsobe transmitted/received during SF 4, such that the schedulinginformation for the UL transmission in the immediate next UL subframefollowing the UpPTS is transmitted/received in a TTI having a leadingboundary occurring at least three subframes prior to SF 7. In someexamples, the scheduling information for the PUSCH in the UpPTS may betransmitted in a PDCCH but not an EPDCCH in SF 4, to provide theLTE/LTE-A UE enough time to decode and process the schedulinginformation for the PUSCH in the UpPTS. Alternatively, schedulinginformation for the PUSCH in the UpPTS in SF 6 and/or schedulinginformation for a UL transmission in SF 7 may be transmitted/received inSF 3, similarly to how scheduling information may be transmitted for aLTE/LTE-A UE that is not capable of latency reduction.

For a ULL UE that is capable of latency reduction (e.g., a UE that has aTTI duration reduction capability), scheduling information for the PUSCHin the UpPTS in SF 6 may be transmitted/received during the second slotof SF 4, such that the scheduling information for the PUSCH in the UpPTSis transmitted/received in a TTI having a leading boundary occurring atleast 2 subframes (or four 0.5 ms ULL TTIs) prior to the UpPTS in SF 6.In some examples, the scheduling information for the PUSCH in the UpPTSmay be transmitted in a PDCCH or an EPDCCH in SF 4. Alternatively,scheduling information for the PUSCH in the UpPTS in SF 6 and/orscheduling information for a UL transmission in SF 7 may betransmitted/received in SF 3 or SF 4 similarly to how schedulinginformation may be transmitted for a LTE/LTE-A UE that is not capable oflatency reduction or a LTE/LTE-A UE that has a scheduling timingreduction capability.

Shortening the scheduling timing for a PUSCH in a UpPTS (e.g.,shortening the time between transmitting/receiving schedulinginformation and the time for receiving/transmitting the PUSCH in theUpPTS) when operating in a CA mode may raise UCI transmission issuesrelated to CA. For example, a CC other than a CC that carries the PUSCHin the UpPTS may determine that UCI should be transmitted on the PUSCHin the UpPTS, and the time that a UE may need to prepare the UCI fortransmission on the PUSCH in the UpPTS may be greater than the lead timethat the scheduling timing provides. In some examples, such a scenariomay be avoided by not allowing transmissions of UCI on a PUSCH in aUpPTS, and transmitting UCI on a PUCCH or PUSCH carried by a CC otherthan the CC that carries the PUSCH in the UpPTS. Additionally oralternatively, the probability of UCI being transmitted on a PUSCH in aUpPTS may be reduced by biasing the selection of a CC for carrying UCIaway from a CC carrying a PUSCH in a UpPTS.

In some examples, HARQ for a PUSCH in a UpPTS may be jointly managedwith HARQ for a UL transmission in a UL subframe (e.g., HARQ for a PUSCHin a UpPTS and HARQ for a transmission in a UL subframe may be mixedwhen the HARQ is for transmissions in a same transport block). Jointmanagement, however, may undesirably increase HARQ overhead in somesubframes of some configurations of a TDD radio frame structure (e.g.,for UL heavy configurations). In some examples, HARQ for a PUSCH in aUpPTS may be separately managed from HARQ for a UL transmission in a ULsubframe (e.g., HARQ for a PUSCH in a UpPTS and HARQ for a transmissionin a UL subframe may not be mixed when the HARQ is for transmissions ina same transport block). In some examples, HARQ for a PUSCH in a UpPTSand/or HARQ for a UL transmission in a UL subframe may betransmitted/received asynchronously. In this case of asynchronous HARQoperation, a HARQ process identity may be included in the controlinformation scheduling PUSCH to indicate the HARQ process with which aPUSCH transmission is associated.

When scheduling information for a PUSCH in a UpPTS and schedulinginformation for a UL transmission in a UL subframe may both betransmitted/received in a same TTI, a base station and UE may usevarious methods to differentiate, within downlink control information(DCI), a first UL grant for the PUSCH in the UpPTS from a second ULgrant for the UL transmission in the UL subframe. In some examples, DCIincluding the first UL grant for the PUSCH may be associated with a DCIformat 0 or DCI format 4, and the second UL grant for the ULtransmission in the UL subframe may be associated with a format, denotedfor convenience of exposition as DCI format 0′ or DCI format 4′.

In some examples, a UL grant for a PUSCH in a UpPTS may be identified(e.g., differentiated from a UL grant for a UL transmission in a ULsubframe) by one or more of: a state of an information field included inDCI, a masking of a control channel including DCI with a predeterminedcyclic redundancy check (CRC) mask, an association of a UL grant with apredetermined decoding candidate, a size of the DCI containing a ULgrant, an identifier of a subframe in which DCI containing a UL grant isreceived, a DCI format, or a combination thereof.

In examples in which a UL grant for a PUSCH in a UpPTS is identifiedbased at least in part on a state of an information field included inDCI, the information field may include, for example, a UL index or a DLassignment index (DAI). In some examples, a UL index of 00 may identifya UL grant for a PUSCH in a UpPTS. For example, a UL index of 00 isapplicable to TDD DL-UL subframe configuration 0 in FIG. 2. In someexamples, a DAI not used for a particular TDD DL-UL subframeconfiguration may be used to identify a UL grant for a PUSCH in a UpPTS(e.g., for TDD DL-UL subframe configuration 6 in FIG. 2, without FDD/TDDCA, or without TDD of different configurations, DAI=1 or DAI=4 may beused, and DAI=2 and DAI=3 may not be used).

In examples in which a UL grant for a PUSCH in a UpPTS is identifiedbased at least in part on a masking (or non-masking) of a controlchannel including DCI (including the UL grant) with a predetermined CRCmask, the UL grant may be transmitted in accordance with DCI format 0′or DCI format 4′ and be scrambled by the CRC mask 0000 0000 0000 0001.When using CRC masking to identify a UL grant for a PUSCH in a UpPTS,indications of antenna switching based on CRC masking may be prohibited,or may made using different CRC masking than is used for identifying aUL grant for a PUSCH in a UpPTS.

In examples in which a UL grant for a PUSCH in a UpPTS is identifiedbased at least in part on its association with a predetermined decodingcandidate (e.g., a decoding candidate having a predetermined length andbeginning at a predetermined resource element (RE)), the UL grant may betransmitted in accordance with a single predetermined decodingcandidate, or may be transmitted in accordance with a decoding candidateselected from a plurality of predetermined decoding candidates allocatedfor transmissions of UL grants for a PUSCH in a UpPTS. Otherpredetermined decoding candidates may be allocated for transmitting a ULgrant for a UL transmission in a UL subframe.

In examples in which a UL grant for a PUSCH in a UpPTS is identifiedbased at least in part on a size of the DCI containing the UL grant, DCIformat 0 and DCI format 0′ may be differentiated by increasing ordecreasing the size of one of the formats (e.g., by extending orcontracting an existing information field or fields), and DCI format 4and DCI format 4′ may be differentiated by increasing or decreasing thesize of one the formats. In some examples, the size of a DCI format maybe increased or decreased to match the size of another DCI format (e.g.,the size of DCI format 1A may be increased or decreased to match thesize of an increased or decreased DCI format 0 size). To limit thenumber of blind decodes that a UE may have to perform, increasing ordecreasing the size of a DCI format compared to the size of another DCIformat may be combined with a restriction on the number of decodingcandidates associated with one or more resource aggregation levels.

In examples in which a UL grant for a PUSCH in a UpPTS is identifiedbased at least in part on an identifier of a subframe in which DCIcontaining a UL grant is received, a UL grant for a PUSCH in a UpPTS maybe transmitted in accordance with DCI format 0 or DCI format 4 in afirst TTI associated with a first identifier, and a UL grant for a ULtransmission in a UL subframe may be transmitted in accordance with DCIformat 0′ or DCI format 4′ in a second TTI associated with a secondidentifier. However, for a TDD DL-UL subframe configuration such as theTDD DL-UL subframe configuration 0 or 6 in FIG. 2, a different method ofidentifying a UL grant for a PUSCH in a UpPTS may be necessary, becausethe number of subframes available for PUSCH transmissions exceeds thenumber of subframes available to carry UL grants.

In examples in which a UL grant for a PUSCH in a UpPTS is identifiedbased at least in part on a DCI format associated with the UL grant, theset of DCI formats that may be used for transmission of the UL grant maybe restricted. For example, DCI format 0′ may be used or DCI format 4′may be used, but a base station may not be allowed to select a DCIformat from a set of DCI formats including both DCI format 0′ and DCIformat 4′.

In some examples, a technique for differentiating a UL grant for a PUSCHin a UpPTS from a UL grant for a UL transmission in a UL subframe may beused for a TTI in which both types of UL grant are transmitted (orexpected to be transmitted), but may not be used for other TTIs.

In some examples, a power control parameter for a PUSCH in a UpPTS maybe based at least in part on a power control parameter for a TTI. Forexample, a power control parameter for the PUSCH in the UpPTS may bebased at least in part on a semi-static relationship (e.g., an offset)between a first power control parameter for the TTI and a second powercontrol parameter for the PUSCH in the UpPTS (e.g., the second controlparameter may be based at least in part on a value of the first powercontrol parameter, multiplied by a ratio of a fixed duration of thePUSCH in the UpPTS to a fixed duration of the TTI). As another example,a power control parameter for the PUSCH in the UpPTS may be based atleast in part on a variable structure of the PUSCH in the UpPTS (e.g., asecond control parameter for the PUSCH in the UpPTS may be based atleast in part on a value of a first power control parameter for a ULtransmission in a UL subframe, multiplied by a ratio of a duration ofthe PUSCH in the UpPTS to a duration of the TTI).

Examples of UCI include periodic channel state information (P-CSI),aperiodic channel state information (A-CSI), a scheduling request (SR),and acknowledgement/non-acknowledgement (ACK/NAK) data. With respect toa PUSCH in a UpPTS, P-CSI to be transmitted on the PUSCH in the UpPTSmay come from a CC carrying the PUSCH in the UpPTS, and when operatingin a CA mode, from other CCs. Similarly, A-CSI transmitted on the PUSCHto be transmitted on the PUSCH in the UpPTS may come from a CC carryingthe PUSCH in the UpPTS, and when operating in a CA mode, from other CCs.In some examples, SRs may not be transmitted on the CC carrying thePUSCH in the UpPTS, and may instead be transmitted on a PCC, which PCCis not the CC carrying the PUSCH in the UpPTS. When DL HARQ timingremains unchanged regardless of whether a PUSCH may be transmitted in aUpPTS, ACK/NAK data may not be transmitted on a PUSCH in a UpPTS.

In some examples, the transmission of UCI (e.g., P-CSI and A-CSI) on aPUSCH in a UpPTS may be supported (or allowed) regardless of whether aCC other than a CC carrying the PUSCH in the UpPTS is available to carrythe UCI. In other examples, the transmission of UCI (e.g., P-CSI andA-CSI) on a PUSCH in a UpPTS may not be supported (or not allowed) whena CC other than the CC carrying the PUSCH in the UpPTS is available tocarry the UCI (e.g., when an uplink TTI is scheduled to be transmittedon at least a first CC while the PUSCH in the UpPTS is transmitted on asecond CC, as may be the case when operating in a CA mode).

In some examples, whether or not to support transmission of UCI (e.g.,P-CSI and A-CSI) on a PUSCH in a UpPTS may be dependent on whether ornot the UE is configured for parallel PUCCH and PUSCH transmission. Ifthe UE is not configured for parallel PUCCH and PUSCH transmission, andif the PUSCH in a UpPTS is the only PUSCH transmission across two ormore CCs in a group configured for carrier aggregation ordual-connectivity for a UE, the PUSCH may be dropped and the UCI can betransmitted on a PUCCH channel. In other words, the UE may skiptransmission of the only PUSCH in a group when there is also UCI due fortransmission. The scheduled PUSCH in a UpPTS in such a case can betreated as an error case. Alternatively, if the PUSCH in a UpPTS is theonly PUSCH transmission in a group across two or more CCs configured forcarrier aggregation or dual-connectivity for a UE, the UCI may beincluded as part of the PUSCH in a UpPTS, instead of being transmittedon a PUCCH channel, in order to avoid parallel PUCCH and PUSCHtransmission. If the UE is configured with parallel PUCCH and PUSCHtransmission, the PUSCH in a UpPTS may or may not be involved in UCItransmission. If the PUSCH in a UpPTS is not to be used for transmittingUCI, a PUCCH channel can be transmitted along with the PUSCH in a UpPTS,thus resulting in parallel PUCCH and PUSCH transmission. If the PUSCH ina UpPTS is involved in transmitting UCI, the PUSCH in a UpPTS maytransmit one or more UCIs, e.g. periodic CSI if due for transmission.

In some examples, a demodulation reference signal (DM-RS) for a PUSCH inan UpPTS may follow a legacy DM-RS, as in the regular UL subframes.Alternatively, the DM-RS pattern for the PUSCH in the UpPTS may use adifferent pattern. As an example, the DM-RS pattern may use a patternsimilar to SRS, where a comb level 2 or 4 may be used. This may allowthe DM-RS for the PUSCH in the UpPTS to be more efficiently multiplexedwith SRS in the UpPTS.

In some examples, a physical HARQ indicator channel (PHICH) fornon-adaptive re-transmissions of the PUSCH in a UpPTS may be located ina downlink subframe, where the same set of PHICH resources may be usedto acknowledge PUSCH transmissions in one or more UL subframes. In orderto differentiate PHICH resources for the PUSCH in a UpPTS and the PUSCHin a UL subframe, an additional offset may be introduced for determiningthe PHICH resource corresponding to the PUSCH in a UpPTS, in addition toother parameters for PHICH resource derivation, such as the starting PRBindex of the PUSCH, the DM-RS cyclic shift of the PUSCH, etc.

FIG. 5 shows a configuration of a subframe 500 including multipleparallel CCs, in accordance with various aspects of the presentdisclosure. By way of example, the CCs may include a first CC 505, asecond CC 510, and a third CC 515. The first CC 505 may be configuredfor downlink use, and the second CC 510 may be configured for uplinkuse, in accordance with a FDD transmission mode between the first CC 505and the second CC 510. The third CC 515 may be configured with a DwPTS520, followed by a GP 525, followed by a UpPTS 530, in accordance with aTDD transmission mode on the third CC 515. A PUSCH may be transmitted inthe UpPTS 530.

In some examples, a transmission of P-CSI, A-CSI, or other UCI on thePUSCH in the UpPTS 530 may not be supported. Thus, the PUSCH in theUpPTS 530 (or the third CC 515) may not be included in a prioritizationof PUSCHs or PUCCHs (or CCs) from which a PUSCH or PUCCH (or CC) forcarrying UCI may be selected. In FIG. 5, P-CSI, A-CSI, or other UCI maybe transmitted on a PUSCH or PUCCH transmitted on the second CC 510. Insome examples, the PUSCH in the UpPTS 530 may not be transmitted whenP-CSI is transmitted on another CC and a UE is not configured forparallel PUCCH and/or PUSCH transmission.

In some examples, a transmission of P-CSI, A-CSI, or other UCI on thePUSCH in the UpPTS 530 may be supported. In these examples, the PUSCH inthe UpPTS 530 (or the third CC 515) may be included in a prioritizationof PUSCHs or PUCCHs (or CCs) from which a PUSCH or PUCCH (or CC) forcarrying UCI may be selected, and a transmission of P-CSI, A-CSI, orother UCI may be made on the PUSCH in the UpPTS 530. In some examples,the PUSCH in the UpPTS 530 (or the third CC 515) may be assigned a lowercell index or lower priority in the prioritization of PUSCHs or PUCCHs(or CCs), which may decrease the probability of the PUSCH in the UpPTS530 (or the third CC 515) from being selected to carry UCI when PUSCHsor PUCCHs (or other CCs, such as the second CC 510) are assigned ahigher cell index or higher priority, and are available to carry UCI.Criteria other than cell index or priority may additionally oralternatively be used when selecting a PUSCH or PUCCH (or CC) to carryUCI.

When a transmission of P-CSI, A-CSI, or other UCI on the PUSCH in theUpPTS 530 is supported (or allowed), a first set of offsets may beconfigured for P-CSI, A-CSI, or other UCI transmitted on the PUSCH inthe UpPTS 530. The first set of offsets may differ from a second set ofoffsets for at least one UCI type configuration for an uplink subframe.The first set of offsets may determine the amount of resources allocatedfor various UCI types that may be transmitted on the PUSCH in the UpPTS530. In some examples, an offset may be a RRC-configured offset (e.g., abeta_offset). Offsets may include offsets for ACK/NAK data, channelquality indicator (CQI)/precoding matrix indicator (PMI), rank indicator(RI)/precoding type indicator (PTI), etc. In some examples, each offsetmay identify a number of REs allocated for a UCI type. The first set ofoffsets may be configured differently from the second set of offsetsbecause the PUSCH in the UpPTS 530 may have a different amount ofresources than a PUSCH in an uplink subframe. Some or all UCI types maybe associated with two offsets. As an example, ACK/NAK and RI/PTI may beassociated with two offsets—one for UL subframes and the other forUpPTS, while CQI may be associated with a single offset applicable toboth UL subframes and UpPTS. As another example, all UCI types may beassociated with two offsets—one for UL subframes and the other forUpPTS.

FIG. 6 shows alternative configurations of a subframe 600 including asix symbol period UpPTS, in accordance with various aspects of thepresent disclosure. In some examples, the subframe 600 may be an exampleof aspects of one of the S subframes included in one of the DL-ULsubframe configurations described with reference to FIG. 2. The subframe600 may include a first slot 605 (Slot 0) followed by a second slot 610(Slot 1). The subframe 600 may include a six symbol period DwPTS 615within the first slot 605, followed by a two symbol GP 620 spanning thefirst slot 605 and the second slot 610, followed by a six symbol periodUpPTS 625 within the second slot 610. A PUSCH may be transmitted in thesix symbol period UpPTS 625. In some examples, the subframe 600 may havea duration of 1 ms.

In some examples, a subset of modulation symbols of a nominal PUSCHconfiguration for a slot may be mapped to the six symbol period UpPTS625. In some examples, the subset of modulation symbols of the nominalPUSCH configuration for a slot may include a temporally last subset ofmodulation symbols of the nominal PUSCH configuration for the slot(e.g., a first symbol of a seven symbol nominal PUSCH configuration fora slot may not be mapped to the six symbol period UpPTS 625, resultingin a DDRDDD symbol pattern being transmitted during the six symbolperiod UpPTS 625, as shown in Alternative 1 630) or a temporally firstsubset of modulation symbols of the nominal PUSCH configuration for theslot (e.g., a last symbol of a seven symbol nominal PUSCH configurationfor a slot may not be transmitted during the six symbol period UpPTS625, resulting in a DDDRDD symbol pattern being transmitted during thesix symbol period UpPTS 625, as shown in Alternative 2 635). The Dsymbols are PUSCH data symbols, and the R symbols are demodulationreference signal transmissions.

In some examples, a pattern of modulation symbols other than a subset ofmodulation symbols of a nominal PUSCH configuration for a slot may bemapped to the six symbol period UpPTS 625. For example, a demodulationreference signal transmission (R symbol) may be mapped to a temporallythird symbol period of the six symbol period UpPTS 625, and PUSCH datasymbols (D symbols) may be mapped to at least some of the other symbolperiods of the six symbol period UpPTS 625, as shown in Alternative 1630; or a demodulation reference signal transmission may be mapped to atemporally fourth symbol period of the six symbol period UpPTS 625, andPUSCH data symbols may be mapped to at least some of the other symbolperiods of the six symbol period UpPTS 625, as shown in Alternative 2635; or a demodulation reference signal transmission may be mapped to atemporally second symbol period and a temporally fifth symbol period ofthe six symbol period UpPTS 625, and PUSCH data symbols may be mapped toat least some of the other symbol periods of the six symbol period UpPTS625, as shown in Alternative 3 640; or demodulation reference signalsmay be mapped to two symbol periods of the six symbol period UpPTS 625,and PUSCH data symbols may be mapped to at least some of the othersymbol periods of the six symbol period UpPTS 625, as shown inAlternative 3 640; or a demodulation reference signal may be mapped toat least a temporally first symbol period of the six symbol period UpPTS625, and PUSCH data symbols may be mapped to at least some of the othersymbol periods of the six symbol period UpPTS 625 (not shown).Configurations in which demodulation reference signals are mapped to atleast two symbol periods of the six symbol period UpPTS 625 may beuseful in that other LTE/LTE-A PUSCH transmissions are transmitted overthe two slots of a subframe, with one demodulation reference signaltransmitted per slot. Additionally or alternatively, the use of someorthogonal cover codes (OCCs) used in MIMO transmissions may require thetransmission of a demodulation reference signal during each of twosymbol periods.

In some examples, a PUSCH may be transmitted during the six symbolperiod UpPTS 625 using one of a plurality of alternative data structuresand demodulation reference signal structures (e.g., one of the datastructures and demodulation reference signal structures associated withAlternative 1 630, Alternative 2 635, or Alternative 3 640), and anetwork access device (e.g., a base station) may transmit an indicationof the data structure and the demodulation reference signal structurethat a UE should use. The indication of the data structure and thedemodulation reference signal structure may include, for example, atleast one of a RRC configuration, or a dynamic indication in downlinkcontrol information (DCI), or a DCI format, or a combination thereof. Insome examples, the dynamic indication in DCI may be implicit. Forexample, when DCI indicates single input, multiple output (SIMO)operation, the use of Alternative 1 630 may be implicitly indicated, orwhen DCI indicates MIMO operation, the use of Alternative 3 640 may beimplicitly indicated.

In some examples, frequency hopping during transmission of a PUSCH in aUpPTS may be enabled (or disabled) based at least in part on a number ofreference symbols to be transmitted in the UpPTS. With reference to FIG.6, frequency hopping may not be enabled for a six symbol period UpPTS625 that includes just one demodulation reference symbol transmission(e.g., a frequency hopping enablement bit may be set to a frequencyhopping disabled state, or may not be transmitted, for Alternative 1 630or Alternative 2 635). However, frequency hopping may be enabled for asix symbol period UpPTS 625 that includes two or more demodulationreference symbol transmissions (e.g., a frequency hopping enablement bitmay or may not be set to a frequency hopping enabled state, or may betransmitted, for Alternative 3 640).

In some examples, multi-cluster resource allocation may or may not besupported for a PUSCH in a UpPTS (e.g., multi-cluster resourceallocation may or may not be supported for any of Alternative 1 630,Alternative 2 635, or Alternative 3 640 in FIG. 6).

In some examples, the use of a cyclic shift or OCC index duringtransmission of a PUSCH in a UpPTS may be enabled (or disabled) based atleast in part on a number of reference symbols to be transmitted in theUpPTS. With reference to FIG. 6, the use of a cyclic shift or OCC indexmay not be enabled for a six symbol period UpPTS 625 that includes justone demodulation reference symbol transmission (e.g., for Alternative 1630 or Alternative 2 635). However, the use of a cyclic shift or OCCindex may be enabled for a six symbol period UpPTS 625 that includes twoor more demodulation reference symbol transmissions (e.g., forAlternative 3 640).

A PUSCH in a UpPTS may or may not be scheduled by a network accessdevice in response to receiving a random access preamble (e.g., aMessage 1 of a random access procedure) from a UE. When a PUSCH in aUpPTS is scheduled in response to receiving a random access preamblefrom a UE, scheduling information for the PUSCH in the UpPTS may betransmitted to the UE in a random access response message (e.g., aMessage 3 of a random access procedure).

FIG. 7 shows a block diagram 700 of an apparatus 715 for use in wirelesscommunication, in accordance with various aspects of the presentdisclosure. The apparatus 715 may be an example of aspects of one ormore of the UEs 115 described with reference to FIG. 1. The apparatus715 may also be or include a processor. The apparatus 715 may include areceiver 710, a wireless communication manager 720, or a transmitter730. Each of these components may be in communication with each other.

The components of the apparatus 715 may, individually or collectively,be implemented using one or more application-specific integratedcircuits (ASICs) adapted to perform some or all of the applicablefunctions in hardware. Alternatively, the functions may be performed byone or more other processing units (or cores), on one or more integratedcircuits. In other examples, others of integrated circuits may be used(e.g., Structured/Platform ASICs, Field Programmable Gate Arrays(FPGAs), a System on Chip (SoC), and/or others of Semi-Custom ICs),which may be programmed in any manner known in the art. The functions ofeach component may also be implemented, in whole or in part, withinstructions embodied in a memory, formatted to be executed by one ormore general or application-specific processors.

In some examples, the receiver 710 may include at least one radiofrequency (RF) receiver, such as at least one RF receiver operable toreceive transmissions over at least one radio frequency spectrum band.In some examples, one or more of the at least one radio frequencyspectrum band may be used for LTE/LTE-A communications, as described,for example, with reference to FIG. 1, 2, 3, 4, 5, or 6. The receiver710 may be used to receive various data or control signals (i.e.,transmissions) over one or more communication links of a wirelesscommunication system, such as one or more communication links of thewireless communication system 100 described with reference to FIG. 1.

In some examples, the transmitter 730 may include at least one RFtransmitter, such as at least one RF transmitter operable to transmitover at least one radio frequency spectrum band. The transmitter 730 maybe used to transmit various data or control signals (i.e.,transmissions) over one or more communication links of a wirelesscommunication system, such as one or more communication links of thewireless communication system 100 described with reference to FIG. 1.

In some examples, the wireless communication manager 720 may be used tomanage one or more aspects of wireless communication for the apparatus715. In some examples, part of the wireless communication manager 720may be incorporated into or shared with the receiver 710 or thetransmitter 730. In some examples, the wireless communication manager720 may include a PUSCH identifier 735, a UCI manager 740, or a PUSCHtransmission manager 745.

The PUSCH identifier 735 may be used to identify a PUSCH to transmit ina UpPTS of a subframe. The UCI manager 740 may be used to determinewhether to transmit UCI on the PUSCH in the UpPTS. The PUSCHtransmission manager 745 may be used to transmit the PUSCH in the UpPTSbased at least in part on the determination made by the UCI manager 740.

FIG. 8 shows a block diagram 800 of a wireless communication manager 820for use in wireless communication, in accordance with various aspects ofthe present disclosure. The wireless communication manager 820 may be anexample of aspects of the wireless communication manager 720 describedwith reference to FIG. 7.

The components of the wireless communication manager 820 may,individually or collectively, be implemented using one or more ASICsadapted to perform some or all of the applicable functions in hardware.Alternatively, the functions may be performed by one or more otherprocessing units (or cores), on one or more integrated circuits. In someother examples, other types of integrated circuits may be used (e.g.,Structured/Platform ASICs, FPGAs, a SoC, and/or other types ofSemi-Custom ICs), which may be programmed in any manner known in theart. The functions of each component may also be implemented, in wholeor in part, with instructions embodied in a memory, formatted to beexecuted by one or more general or application-specific processors.

In some examples, the wireless communication manager 820 may be used tomanage one or more aspects of wireless communication for a UE orapparatus, such as one of the UEs 115 described with reference to FIG.1, or one of the apparatus 715 described with reference to FIG. 7. Insome examples, part of the wireless communication manager 820 may beincorporated into or shared with a receiver or a transmitter (e.g., thereceiver 710 or the transmitter 730 described with reference to FIG. 7).In some examples, the wireless communication manager 820 may include anoptional random access manager 850, an optional carrier aggregationmanager 855, a PUSCH identifier 835, a UCI manager 840, a PUSCHtransmission manager 845, or a HARQ manager 875. The PUSCH identifiermay include a PUSCH scheduling manager 860. The UCI manager 840 mayinclude an optional UCI CC selector 865. The PUSCH transmission manager845 may include a power controller 870.

The random access manager 850 may be used, under some conditions, totransmit a random access preamble.

The PUSCH identifier 835 may be used to identify a PUSCH to transmit ina UpPTS of a subframe.

The PUSCH scheduling manager 860 may be used to receive, during a TTI,scheduling information for the PUSCH in the UpPTS. A timing of the TTImay be based at least in part on a latency reduction capability of a UEthat includes the wireless communication manager 820. In some examples,the latency reduction capability of the UE may include at least one of ascheduling timing reduction capability, a TTI duration reductioncapability, or a combination thereof. In some examples, the timing ofthe TTI in which the scheduling information is received may include aleading boundary occurring at least two subframes prior to the UpPTS, ora leading boundary occurring at least 2.5 subframes prior to the UpPTS.In some examples, the scheduling information may include a first offsetthat differs from a second offset for at least one UCI typeconfiguration received for an uplink subframe. In some examples, part orall of the scheduling information may be received in DCI or RRCsignaling. In some examples, the PUSCH scheduling manager 860 mayreceive a random access response message scheduling the PUSCH in theUpPTS. The random access response message may be received in response tothe random access manager 850 transmitting a random access preamble.

In some examples, the PUSCH scheduling manager 860 may be used toreceive DCI. The DCI may be received as part of the received schedulinginformation. In some examples, the PUSCH scheduling manager 860 mayidentify an uplink grant for the PUSCH in the UpPTS, received in theDCI, based at least in part on a state of an information field includedin the DCI, a masking of a control channel including the DCI with apredetermined CRC mask, an association of the uplink grant with apredetermined decoding candidate, a size of the DCI, an identifier of asubframe in which the DCI is received, a DCI format, or a combinationthereof. In some examples, the PUSCH scheduling manager 860 maydetermine a size of the DCI. In some examples, the PUSCH schedulingmanager 860 may identify, within the DCI, at least one decodingcandidate for an uplink grant for the PUSCH in the UpPTS. The at leastone decoding candidate may be based at least in part on the size of theDCI.

The carrier aggregation manager 855 may be used to determine whether anuplink TTI is scheduled to be transmitted on at least a first CC whilethe PUSCH in the UpPTS is transmitted on a second CC. Additionally oralternatively, the carrier aggregation manager 855 may be used todetermine whether the PUSCH in the UpPTS is scheduled to be transmittedwhen operating in a carrier aggregation mode.

The UCI manager 840 may be used to determine whether to transmit UCI onthe PUSCH in the UpPTS. In some examples, the determination made by theUCI manager 840 may be based at least in part on one of a determinationsmade by the carrier aggregation manager 855. For example, the UCImanager 840 may determine to transmit UCI on the PUSCH in the UpPTS whenit is determined by the carrier aggregation manager 855 that an uplinkTTI is scheduled to be transmitted at least the first CC. In someexamples, the determination made by the UCI manager 840 may be based atleast in part on a determination that the PUSCH in the UpPTS isscheduled to be transmitted when operating in a carrier aggregationmode. For example, when operating in a carrier aggregation mode, adetermination may be made by the UCI manager 840 to not transmit, on thePUSCH in the UpPTS, at least one of periodic CSI, aperiodic CSI, UCI, ora combination thereof. When operating in a carrier aggregation mode, thedetermination made by the UCI manager 840 may additionally oralternatively include determining to transmit, in parallel with thePUSCH in the UpPTS, and on a CC that does not carry the PUSCH in theUpPTS, at least one of: periodic CSI, aperiodic CSI, UCI, or acombination thereof. Alternatively, when operating in a carrieraggregation mode, a determination may be made by the UCI manager 840 totransmit at least one of periodic CSI, aperiodic CSI, UCI, or acombination thereof on the PUSCH in the UpPTS.

The UCI CC selector 865 may be used to select a CC for transmitting UCI.In some examples, the CC may be selected based at least in part on aprioritization of CCs that biases CC selection away from a CC carryingthe PUSCH in the UpPTS.

The power controller 870 may be used to identify a first power controlparameter for a TTI, and determine a second power control parameter forthe PUSCH in the UpPTS based at least in part on the first power controlparameter for the TTI. In some examples, the second power controlparameter may be determined based at least in part on a semi-staticrelationship between the first power control parameter and the secondcontrol parameter, or based at least in part on a variable structure ofthe PUSCH in the UpPTS.

The PUSCH transmission manager 845 may be used to transmit the PUSCH inthe UpPTS based at least in part on a determination made by the UCImanager 840. In some examples, the PUSCH transmission manager 845 mayadditionally or alternatively be used to determine, based at least inpart on a number of reference symbols to be transmitted in the UpPTS,whether to enable at least one of: frequency hopping during transmissionof the PUSCH in the UpPTS, use of an OCC during transmission of thePUSCH in the UpPTS, or a combination thereof.

The HARQ manager 875 may be used to manage HARQ. In some examples,managing HARQ may include at least one of: separately managing uplinkHARQ for the PUSCH in the UpPTS and uplink HARQ for PUSCH transmissionsin uplink TTIs, jointly managing the uplink HARQ for the PUSCH in theUpPTS and the uplink HARQ for PUSCH transmissions in uplink TTIs, orreceiving the uplink HARQ for the PUSCH in the UpPTS and the uplink HARQfor PUSCH transmissions in uplink TTIs asynchronously.

FIG. 9 shows a block diagram 900 of an apparatus 905 for use in wirelesscommunication, in accordance with various aspects of the presentdisclosure. The apparatus 905 may be an example of aspects of a networkaccess device, such as one or more of the base stations 105 describedwith reference to FIG. 1. The apparatus 905 may also be or include aprocessor. The apparatus 905 may include a receiver 910, a wirelesscommunication manager 920, or a transmitter 930. Each of thesecomponents may be in communication with each other.

The components of the apparatus 905 may, individually or collectively,be implemented using one or more ASICs adapted to perform some or all ofthe applicable functions in hardware. Alternatively, the functions maybe performed by one or more other processing units (or cores), on one ormore integrated circuits. In other examples, others of integratedcircuits may be used (e.g., Structured/Platform ASICs, FPGAs, a SoC,and/or others of Semi-Custom ICs), which may be programmed in any mannerknown in the art. The functions of each component may also beimplemented, in whole or in part, with instructions embodied in amemory, formatted to be executed by one or more general orapplication-specific processors.

In some examples, the receiver 910 may include at least one RF receiver,such as at least one RF receiver operable to receive transmissions overat least one radio frequency spectrum band. In some examples, one ormore of the at least one radio frequency spectrum band may be used forLTE/LTE-A communications, as described, for example, with reference toFIG. 1, 2, 3, 4, 5, or 6. The receiver 910 may be used to receivevarious data or control signals (i.e., transmissions) over one or morecommunication links of a wireless communication system, such as one ormore communication links of the wireless communication system 100described with reference to FIG. 1.

In some examples, the transmitter 930 may include at least one RFtransmitter, such as at least one RF transmitter operable to transmitover at least one radio frequency spectrum band. The transmitter 930 maybe used to transmit various data or control signals (i.e.,transmissions) over one or more communication links of a wirelesscommunication system, such as one or more communication links of thewireless communication system 100 described with reference to FIG. 1.

In some examples, the wireless communication manager 920 may be used tomanage one or more aspects of wireless communication for the apparatus905. In some examples, part of the wireless communication manager 920may be incorporated into or shared with the receiver 910 or thetransmitter 930. In some examples, the wireless communication manager920 may include a UCI manager 935, a PUSCH scheduler 940, or ascheduling information transmission manager 945.

The UCI manager 935 may be used to determine whether to schedule atransmission of UCI on a PUSCH in a UpPTS of a subframe. The PUSCHscheduler 940 may be used to schedule the PUSCH in the UpPTS based atleast in part on the determination made by the UCI manager 935. Thescheduling information transmission manager 945 may be used to transmit,to a UE, scheduling information for the PUSCH in the UpPTS.

FIG. 10 shows a block diagram 1000 of a wireless communication manager1020 for use in wireless communication, in accordance with variousaspects of the present disclosure. The wireless communication manager1020 may be an example of aspects of the wireless communication manager920 described with reference to FIG. 9.

The components of the wireless communication manager 1020 may,individually or collectively, be implemented using one or more ASICsadapted to perform some or all of the applicable functions in hardware.Alternatively, the functions may be performed by one or more otherprocessing units (or cores), on one or more integrated circuits. In someother examples, other types of integrated circuits may be used (e.g.,Structured/Platform ASICs, FPGAs, a SoC, and/or other types ofSemi-Custom ICs), which may be programmed in any manner known in theart. The functions of each component may also be implemented, in wholeor in part, with instructions embodied in a memory, formatted to beexecuted by one or more general or application-specific processors.

In some examples, the wireless communication manager 1020 may be used tomanage one or more aspects of wireless communication for a networkaccess device or apparatus, such as one of the base stations 105described with reference to FIG. 1, or one of the apparatus 905described with reference to FIG. 9. In some examples, part of thewireless communication manager 1020 may be incorporated into or sharedwith a receiver or a transmitter (e.g., the receiver 910 or thetransmitter 930 described with reference to FIG. 9). In some examples,the wireless communication manager 1020 may include an optional randomaccess manager 1050, a UCI manager 1035, a PUSCH scheduler 1040, ascheduling information transmission manager 1045, or a HARQ manager1055.

The random access manager 1050 may be used to receive a random accesspreamble.

The UCI manager 1035 may be used to determine whether to schedule atransmission of UCI on a PUSCH in a UpPTS of a subframe.

The PUSCH scheduler 1040 may be used to schedule the PUSCH in the UpPTSbased at least in part on the determination made by the UCI manager 935.In some examples, the PUSCH in the UpPTS may be scheduled in response tothe random access manager 1050 receiving a random access preamble. Insome examples, the PUSCH scheduler 1040 may select a first offset forscheduling information for the PUSCH in the UpPTS. In some examples, thefirst offset may differ from a second offset for at least one UCI typeconfiguration selected for an uplink subframe.

The scheduling information transmission manager 1045 may be used totransmit, to a UE, scheduling information for the PUSCH in the UpPTS. Insome examples, the first offset may be indicated in the schedulinginformation. In some examples, the scheduling information transmissionmanager 1045 may select a timing of a TTI in which the schedulinginformation for the PUSCH in the UpPTS is transmitted. The TTI may beselected based at least in part on a latency reduction capability of theUE. In some examples, the latency reduction capability of the UE mayinclude at least one of a scheduling timing reduction capability, a TTIduration reduction capability, or a combination thereof. In someexamples, the timing of the TTI in which the scheduling information istransmitted may include a leading boundary occurring at least twosubframes prior to the UpPTS, or a leading boundary occurring at least2.5 subframes prior to the UpPTS. In some examples, the schedulinginformation transmission manager 1045 may transmit DCI to the UE. Insome examples, the scheduling information transmission manager 1045 mayindicate the presence of an uplink grant for the PUSCH in the UpPTS inthe DCI. The indication may be based at least in part on: a state of aninformation field included in the DCI, a masking of a control channelincluding the DCI with a predetermined CRC mask, an association of theuplink grant with a predetermined decoding candidate, a size of the DCI,an identifier of a subframe in which the DCI is received, a DCI format,or a combination thereof.

The HARQ manager 1055 may be used to manage HARQ. In some examples,managing HARQ may include at least one of: separately managing uplinkHARQ for the PUSCH in the UpPTS and uplink HARQ for PUSCH transmissionsin uplink TTIs, jointly managing the uplink HARQ for the PUSCH in theUpPTS and the uplink HARQ for PUSCH transmissions in uplink TTIs, ortransmitting the uplink HARQ for the PUSCH in the UpPTS and the uplinkHARQ for PUSCH transmissions in uplink TTIs asynchronously.

FIG. 11 shows a block diagram 1100 of a UE 1115 for use in wirelesscommunication, in accordance with various aspects of the presentdisclosure. The UE 1115 may be included or be part of a personalcomputer (e.g., a laptop computer, a netbook computer, a tabletcomputer, etc.), a cellular telephone, a PDA, a DVR, an internetappliance, a gaming console, an e-reader, etc. The UE 1115 may, in someexamples, have an internal power supply (not shown), such as a smallbattery, to facilitate mobile operation. In some examples, the UE 1115may be an example of aspects of one or more of the UEs 115 describedwith reference to FIG. 1, or aspects of the apparatus 715 described withreference to FIG. 7. The UE 1115 may be configured to implement at leastsome of the UE features and functions described with reference to FIG.1, 2, 3, 4, 5, 6, 7, or 8.

The UE 1115 may include a UE processor 1110, a UE memory 1120, at leastone UE transceiver (represented by UE transceiver(s) 1130), at least oneUE antenna (represented by UE antenna(s) 1140), or a UE wirelesscommunication manager 1150. Each of these components may be incommunication with each other, directly or indirectly, over one or moreUE buses 1135.

The UE memory 1120 may include random access memory (RAM) or read-onlymemory (ROM). The UE memory 1120 may store computer-readable,computer-executable code 1125 containing instructions that areconfigured to, when executed, cause the UE processor 1110 to performvarious functions described herein related to wireless communication,including, for example, identifying a PUSCH to transmit in a UpPTS of asubframe, determining whether to transmit UCI on the PUSCH in the UpPTS,and transmitting the PUSCH in the UpPTS based at least in part on thedetermining. Alternatively, the computer-executable code 1125 may not bedirectly executable by the UE processor 1110 but be configured to causethe UE 1115 (e.g., when compiled and executed) to perform various of thefunctions described herein.

The UE processor 1110 may include an intelligent hardware device, e.g.,a central processing unit (CPU), a microcontroller, an ASIC, etc. The UEprocessor 1110 may process information received through the UEtransceiver(s) 1130 or information to be sent to the UE transceiver(s)1130 for transmission through the UE antenna(s) 1140. The UE processor1110 may handle, alone or in connection with the UE wirelesscommunication manager 1150, various aspects of communicating over (ormanaging communications over) one or more radio frequency spectrumbands.

The UE transceiver(s) 1130 may include a modem configured to modulatepackets and provide the modulated packets to the UE antenna(s) 1140 fortransmission, and to demodulate packets received from the antenna(s)1140. The UE transceiver(s) 1130 may, in some examples, be implementedas one or more transmitters and one or more separate receivers. The UEtransceiver(s) 1130 may support communications over one or more wirelesscommunication links. The UE transceiver(s) 1130 may be configured tocommunicate bi-directionally, via the UE antenna(s) 1140, with one ormore network access devices or other apparatuses, such as one or more ofthe base stations 105 described with reference to FIG. 1, or theapparatus 905 described with reference to FIG. 9. While the UE 1115 mayinclude a single UE antenna, there may be examples in which the UE 1115may include multiple UE antennas.

The UE wireless communication manager 1150 may be configured to performor control some or all of the UE features or functions described withreference to FIG. 1, 2, 3, 4, 5, 6, 7, or 8. The UE wirelesscommunication manager 1150, or portions of it, may include a processor,or some or all of the functions of the UE wireless communication manager1150 may be performed by the UE processor 1110 or in connection with theUE processor 1110. In some examples, the UE wireless communicationmanager 1150 may be an example of the wireless communication manager 720or 820 described with reference to FIG. 7 or 8.

FIG. 12 shows a block diagram 1200 of a base station 1205 (e.g., a basestation forming part or all of an eNB) for use in wirelesscommunication, in accordance with various aspects of the presentdisclosure. In some examples, the base station 1205 may be an example ofaspects of one or more of the base stations 105 described with referenceto FIG. 1, or aspects of the apparatus 1105 described with reference toFIG. 1. The base station 1205 may be configured to implement orfacilitate at least some of the network access device or base stationfeatures and functions described with reference to FIG. 1, 2, 3, 4, 5,6, 7, 8, 9, 10, 11, or 12.

The base station 1205 may include a base station processor 1210, a basestation memory 1220, at least one base station transceiver (representedby base station transceiver(s) 1250), at least one base station antenna(represented by base station antenna(s) 1255), or a base stationwireless communication manager 1260. The base station 1205 may alsoinclude one or more of a network access device communicator 1230 or anetwork communicator 1240. Each of these components may be incommunication with each other, directly or indirectly, over one or morebase station buses 1235.

The base station memory 1220 may include RAM or ROM. The base stationmemory 1220 may store computer-readable, computer-executable code 1225containing instructions that are configured to, when executed, cause thebase station processor 1210 to perform various functions describedherein related to wireless communication, including, for example,determining whether to schedule a transmission of UCI on a PUSCH in aUpPTS of a subframe, scheduling the PUSCH in the UpPTS based at least inpart on the determining, and transmitting, to a UE, schedulinginformation for the PUSCH in the UpPTS. Alternatively, thecomputer-executable code 1225 may not be directly executable by the basestation processor 1210 but be configured to cause the base station 1205(e.g., when compiled and executed) to perform various of the functionsdescribed herein.

The base station processor 1210 may include an intelligent hardwaredevice, e.g., a CPU, a microcontroller, an ASIC, etc. The base stationprocessor 1210 may process information received through the base stationtransceiver(s) 1250, the network access device communicator 1230, or thenetwork communicator 1240. The base station processor 1210 may alsoprocess information to be sent to the base station transceiver(s) 1250for transmission through the base station antenna(s) 1255, to thenetwork access device communicator 1230, for transmission to one or moreother network access devices (e.g., the base station 1205-a or the basestation 1205-b), or to the network communicator 1240 for transmission toa core network 1290, which may be an example of one or more aspects ofthe core network 130 described with reference to FIG. 1. The basestation processor 1210 may handle, alone or in connection with the basestation wireless communication manager 1260, various aspects ofcommunicating over (or managing communications over) one or more radiofrequency spectrum bands.

The base station transceiver(s) 1250 may include a modem configured tomodulate packets and provide the modulated packets to the base stationantenna(s) 1255 for transmission, and to demodulate packets receivedfrom the base station antenna(s) 1255. The base station transceiver(s)1250 may, in some examples, be implemented as one or more transmittersand one or more separate receivers. The base station transceiver(s) 1250may support communication over one or more wireless communication links.The base station transceiver(s) 1250 may be configured to communicatebi-directionally, via the base station antenna(s) 1255, with one or moreUEs or other apparatuses, such as one or more of the UEs 115 or 1115described with reference to FIG. 1 or 11, or the apparatus 715,described with reference to FIG. 7. The base station 1205 may, forexample, include multiple base station antennas (e.g., an antennaarray). The base station 1205 may communicate with the core network 1290through the network communicator 1240. The base station 1205 may alsocommunicate with other network access devices, such as the base station1205-a or the base station 1205-b, using the network access devicecommunicator 1230.

The base station wireless communication manager 1260 may be configuredto perform or control some or all of the network access device or basestation features or functions described with reference to FIG. 1, 2, 3,4, 5, 6, 9, or 10. The base station wireless communication manager 1260,or portions of it, may include a processor, or some or all of thefunctions of the base station wireless communication manager 1260 may beperformed by the base station processor 1210 or in connection with thebase station processor 1210. In some examples, the base station wirelesscommunication manager 1260 may be an example of the wirelesscommunication manager 920 or 1020 described with reference to FIG. 9 or10.

FIG. 13 is a flow chart illustrating an example of a method 1300 forwireless communication at a UE, in accordance with various aspects ofthe present disclosure. For clarity, the method 1300 is described belowwith reference to a UE including aspects of one or more of the UEs 115or 1115 described with reference to FIG. 1 or 11, or aspects of theapparatus 715 described with reference to FIG. 7. In some examples, a UEmay execute one or more sets of codes to control the functional elementsof the UE to perform the functions described below. Additionally oralternatively, the UE may perform one or more of the functions describedbelow using special-purpose hardware.

At block 1305, the method 1300 may include identifying a PUSCH totransmit in a UpPTS of a subframe. The operations at block 1305 may beperformed using the wireless communication manager 720 or 820 describedwith reference to FIG. 7 or 8, the UE wireless communication manager1150 described with reference to FIG. 11, or the PUSCH identifier 735 or835 described with reference to FIG. 7 or 8.

At block 1310, the method 1300 may include determining whether totransmit UCI on the PUSCH in the UpPTS. The operations at block 1310 maybe performed using the wireless communication manager 720 or 820described with reference to FIG. 7 or 8, the UE wireless communicationmanager 1150 described with reference to FIG. 11, or the UCI manager 740or 840 described with reference to FIG. 7 or 8.

At block 1315, the method 1300 may include transmitting the PUSCH in theUpPTS based at least in part on the determination made at block 1310.The operations at block 1315 may be performed using the wirelesscommunication manager 720 or 820 described with reference to FIG. 7 or8, the UE wireless communication manager 1150 described with referenceto FIG. 11, or the PUSCH transmission manager 745 or 845 described withreference to FIG. 7 or 8.

FIG. 14 is a flow chart illustrating an example of a method 1400 forwireless communication at a UE, in accordance with various aspects ofthe present disclosure. For clarity, the method 1400 is described belowwith reference to a UE including aspects of one or more of the UEs 115or 1115 described with reference to FIG. 1 or 11, or aspects of theapparatus 715 described with reference to FIG. 7. In some examples, a UEmay execute one or more sets of codes to control the functional elementsof the UE to perform the functions described below. Additionally oralternatively, the UE may perform one or more of the functions describedbelow using special-purpose hardware.

At block 1405, the method 1400 may optionally include transmitting arandom access preamble. The operations at block 1405 may be performedusing the wireless communication manager 720 or 820 described withreference to FIG. 7 or 8, the UE wireless communication manager 1150described with reference to FIG. 11, or the random access manager 850described with reference to FIG. 8.

At one or more of blocks 1410, 1415, or 1420, the method 1400 mayinclude identifying a PUSCH to transmit in a UpPTS of a subframe. Atblock 1410, the method 1400 may include receiving, during a TTI,scheduling information for the PUSCH in the UpPTS. A timing of the TTImay be based at least in part on a latency reduction capability of theUE. In some examples, the latency reduction capability of the UE mayinclude at least one of a scheduling timing reduction capability, a TTIduration reduction capability, or a combination thereof. In someexamples, the timing of the TTI in which the scheduling information isreceived may include a leading boundary occurring at least two subframesprior to the UpPTS, or a leading boundary occurring at least 2.5subframes prior to the UpPTS. In some examples, the schedulinginformation may include a first offset that differs from a second offsetfor at least one UCI type configuration received for an uplink subframe.In some examples, part or all of the scheduling information may bereceived in DCI or RRC signaling. In some examples, the operations atblock 1410 may include receiving a random access response messagescheduling the PUSCH in the UpPTS. The random access response messagemay be received in response to transmitting a random access preamble atblock 1405. The operations at block 1410 may be performed using thewireless communication manager 720 or 820 described with reference toFIG. 7 or 8, the UE wireless communication manager 1150 described withreference to FIG. 11, the PUSCH identifier 735 or 835 described withreference to FIG. 7 or 8, or the PUSCH scheduling manager 860 describedwith reference to FIG. 8.

At block 1415, the method 1400 may include receiving DCI. In someexamples, the DCI may be received as part of receiving the schedulinginformation at block 1410. In some examples, the operations at block1415 may include identifying an uplink grant for the PUSCH in the UpPTS,received in the DCI, based at least in part on a state of an informationfield included in the DCI, a masking of a control channel including theDCI with a predetermined CRC mask, an association of the uplink grantwith a predetermined decoding candidate, a size of the DCI, anidentifier of a subframe in which the DCI is received, a DCI format, ora combination thereof. In some examples, the operations at block 1415may include determining a size of the DCI. In some examples, theoperations at block 1415 may include identifying, within the DCI, atleast one decoding candidate for an uplink grant for the PUSCH in theUpPTS. The at least one decoding candidate may be based at least in parton the size of the DCI. The operations at block 1415 may be performedusing the wireless communication manager 720 or 820 described withreference to FIG. 7 or 8, the UE wireless communication manager 1150described with reference to FIG. 11, the PUSCH identifier 735 or 835described with reference to FIG. 7 or 8, or the PUSCH scheduling manager860 described with reference to FIG. 8.

At block 1420, the method 1400 may optionally include determiningwhether an uplink TTI is scheduled to be transmitted on at least a firstCC while the PUSCH in the UpPTS is transmitted on a second CC, ordetermining whether the PUSCH in the UpPTS is scheduled to betransmitted when operating in a carrier aggregation mode. The operationsat block 1420 may be performed using the wireless communication manager720 or 820 described with reference to FIG. 7 or 8, the UE wirelesscommunication manager 1150 described with reference to FIG. 11, or thecarrier aggregation manager 855 described with reference to FIG. 8.

At block 1425, the method 1400 may include determining whether totransmit UCI on the PUSCH in the UpPTS. In some examples, thedetermination made at block 1425 may be based at least in part on one ofthe determinations made at block 1420. For example, the method 1400 mayinclude determining to transmit UCI on the PUSCH in the UpPTS when it isdetermined at block 1420 that an uplink TTI is scheduled to betransmitted at least the first CC. In some examples, the determinationmade at block 1425 may be based at least in part on determining thePUSCH in the UpPTS is scheduled to be transmitted when operating in acarrier aggregation mode. For example, when operating in a carrieraggregation mode, a determination may be made at block 1425 to nottransmit, on the PUSCH in the UpPTS, at least one of periodic CSI,aperiodic CSI, UCI, or a combination thereof. When operating in acarrier aggregation mode, the determination made at block 1425 mayadditionally or alternatively include determining to transmit, inparallel with the PUSCH in the UpPTS, and on a CC that does not carrythe PUSCH in the UpPTS, at least one of: periodic CSI, aperiodic CSI,UCI, or a combination thereof. Alternatively, when operating in acarrier aggregation mode, a determination may be made at block 1425 totransmit at least one of periodic CSI, aperiodic CSI, UCI, or acombination thereof on the PUSCH in the UpPTS. The operations at block1425 may be performed using the wireless communication manager 720 or820 described with reference to FIG. 7 or 8, the UE wirelesscommunication manager 1150 described with reference to FIG. 11, or theUCI manager 740 or 840 described with reference to FIG. 7 or 8.

At block 1430, the method 1400 may optionally include selecting a CC fortransmitting UCI. In some examples, the CC may be selected based atleast in part on a prioritization of CCs that biases CC selection awayfrom a CC carrying the PUSCH in the UpPTS. The operations at block 1430may be performed using the wireless communication manager 720 or 820described with reference to FIG. 7 or 8, the UE wireless communicationmanager 1150 described with reference to FIG. 11, the UCI manager 740 or840 described with reference to FIG. 7 or 8, or the UCI CC selector 865described with reference to FIG. 8.

At block 1435, the method 1400 may optionally include determining, basedat least in part on a number of reference symbols to be transmitted inthe UpPTS, whether to enable at least one of: frequency hopping duringtransmission of the PUSCH in the UpPTS, use of an OCC duringtransmission of the PUSCH in the UpPTS, or a combination thereof. Theoperations at block 1435 may be performed using the wirelesscommunication manager 720 or 820 described with reference to FIG. 7 or8, the UE wireless communication manager 1150 described with referenceto FIG. 11, or the PUSCH transmission manager 745 or 845 described withreference to FIG. 7 or 8.

At block 1440, the method 1400 may optionally include identifying afirst power control parameter for a TTI. The operations at block 1425may be performed using the wireless communication manager 720 or 820described with reference to FIG. 7 or 8, the UE wireless communicationmanager 1140 described with reference to FIG. 11, the PUSCH transmissionmanager 745 or 845 described with reference to FIG. 7 or 8, or the powercontroller 870 described with reference to FIG. 8.

At block 1445, the method 1400 may optionally include determining asecond power control parameter for the PUSCH in the UpPTS based at leastin part on the first power control parameter for the TTI. In someexamples, the second power control parameter may be determined based atleast in part on a semi-static relationship between the first powercontrol parameter and the second control parameter, or based at least inpart on a variable structure of the PUSCH in the UpPTS. The operationsat block 1425 may be performed using the wireless communication manager720 or 820 described with reference to FIG. 7 or 8, the UE wirelesscommunication manager 1145 described with reference to FIG. 11, thePUSCH transmission manager 745 or 845 described with reference to FIG. 7or 8, or the power controller 870 described with reference to FIG. 8.

At block 1450, the method 1400 may include transmitting the PUSCH in theUpPTS based at least in part on the determination made at block 1425.The operations at block 1450 may be performed using the wirelesscommunication manager 720 or 820 described with reference to FIG. 7 or8, the UE wireless communication manager 1150 described with referenceto FIG. 11, or the PUSCH transmission manager 745 or 845 described withreference to FIG. 7 or 8.

At block 1455, the method 1400 may include managing HARQ. In someexamples, managing HARQ may include at least one of: separately managinguplink HARQ for the PUSCH in the UpPTS and uplink HARQ for PUSCHtransmissions in uplink TTIs, jointly managing the uplink HARQ for thePUSCH in the UpPTS and the uplink HARQ for PUSCH transmissions in uplinkTTIs, or receiving the uplink HARQ for the PUSCH in the UpPTS and theuplink HARQ for PUSCH transmissions in uplink TTIs asynchronously. Theoperations at block 1455 may be performed using the wirelesscommunication manager 720 or 820 described with reference to FIG. 7 or8, the UE wireless communication manager 1150 described with referenceto FIG. 11, or the HARQ manager 875 described with reference to FIG. 8.

FIG. 15 is a flow chart illustrating an example of a method 1500 forwireless communication at a network access device (e.g., a basestation), in accordance with various aspects of the present disclosure.For clarity, the method 1500 is described below with reference to anetwork access device including aspects of one or more of the basestations 105 or 1205 described with reference to FIG. 1 or 12, oraspects of the apparatus 905 described with reference to FIG. 9. In someexamples, a base station may execute one or more sets of codes tocontrol the functional elements of the base station to perform thefunctions described below. Additionally or alternatively, the basestation may perform one or more of the functions described below usingspecial-purpose hardware.

At block 1505, the method 1500 may include determining whether toschedule a transmission of UCI on a PUSCH in a UpPTS of a subframe. Theoperations at block 1505 may be performed using the wirelesscommunication manager 920 or 1020 described with reference to FIG. 9 or10, the base station wireless communication manager 1260 described withreference to FIG. 12, or the UCI manager 935 or 1035 described withreference to FIG. 9 or 10.

At block 1510, the method 1500 may include scheduling the PUSCH in theUpPTS based at least in part on the determining. The operations at block1510 may be performed using the wireless communication manager 920 or1020 described with reference to FIG. 9 or 10, the base station wirelesscommunication manager 1260 described with reference to FIG. 12, or thePUSCH scheduler 940 or 1040 described with reference to FIG. 9 or 10.

At block 1515, the method 1500 may include transmitting, to a UE,scheduling information for the PUSCH in the UpPTS. The operations atblock 1515 may be performed using the wireless communication manager 920or 1020 described with reference to FIG. 9 or 10, the base stationwireless communication manager 1260 described with reference to FIG. 12,or the scheduling information transmission manager 945 or 1045 describedwith reference to FIG. 9 or 10.

FIG. 16 is a flow chart illustrating an example of a method 1600 forwireless communication at a network access device (e.g., a basestation), in accordance with various aspects of the present disclosure.For clarity, the method 1600 is described below with reference to anetwork access device including aspects of one or more of the basestations 105 or 1205 described with reference to FIG. 1 or 12, oraspects of the apparatus 905 described with reference to FIG. 9. In someexamples, a base station may execute one or more sets of codes tocontrol the functional elements of the base station to perform thefunctions described below. Additionally or alternatively, the basestation may perform one or more of the functions described below usingspecial-purpose hardware.

At block 1605, the method 1600 may optionally include receiving a randomaccess preamble. The operations at block 1605 may be performed using thewireless communication manager 920 or 1020 described with reference toFIG. 9 or 10, the base station wireless communication manager 1260described with reference to FIG. 12, or the random access manager 1050described with reference to FIG. 10.

At block 1610, the method 1600 may include determining whether toschedule a transmission of UCI on a PUSCH in a UpPTS of a subframe. Theoperations at block 1610 may be performed using the wirelesscommunication manager 920 or 1020 described with reference to FIG. 9 or10, the base station wireless communication manager 1260 described withreference to FIG. 12, or the UCI manager 935 or 1035 described withreference to FIG. 9 or 10.

At block 1615, the method 1600 may include scheduling the PUSCH in theUpPTS based at least in part on the determination made at block 1610. Insome examples, the PUSCH in the UpPTS may be scheduled in response toreceiving a random access preamble at block 1605. In some examples, partor all of the scheduling information may be transmitted in DCI or RRCsignaling. The operations at block 1615 may be performed using thewireless communication manager 920 or 1020 described with reference toFIG. 9 or 10, the base station wireless communication manager 1260described with reference to FIG. 12, or the PUSCH scheduler 940 or 1040described with reference to FIG. 9 or 10.

At block 1620, the method 1600 may optionally include selecting a firstoffset for scheduling information for the PUSCH in the UpPTS. In someexamples, the first offset may differ from a second offset for at leastone UCI type configuration selected for an uplink subframe. Theoperations at block 1620 may be performed using the wirelesscommunication manager 920 or 1020 described with reference to FIG. 9 or10, the base station wireless communication manager 1260 described withreference to FIG. 12, or the PUSCH scheduler 940 or 1040 described withreference to FIG. 9 or 10.

At block 1625, the method 1600 may optionally include selecting a timingof a TTI in which the scheduling information for the PUSCH in the UpPTSis to be transmitted. The TTI may be selected based at least in part ona latency reduction capability of the UE. In some examples, the latencyreduction capability of the UE may include at least one of a schedulingtiming reduction capability, a TTI duration reduction capability, or acombination thereof. In some examples, the timing of the TTI in whichthe scheduling information is transmitted may include a leading boundaryoccurring at least two subframes prior to the UpPTS, or a leadingboundary occurring at least 2.5 subframes prior to the UpPTS. Theoperations at block 1625 may be performed using the wirelesscommunication manager 920 or 1020 described with reference to FIG. 9 or10, the base station wireless communication manager 1260 described withreference to FIG. 12, or the scheduling information transmission manager945 or 1045 described with reference to FIG. 9 or 10.

At block 1630, the method 1600 may include transmitting, to the UE, thescheduling information for the PUSCH in the UpPTS. In some examples, thefirst offset may be indicated in the scheduling information. Theoperations at block 1630 may be performed using the wirelesscommunication manager 920 or 1020 described with reference to FIG. 9 or10, the base station wireless communication manager 1260 described withreference to FIG. 12, or the scheduling information transmission manager945 or 1045 described with reference to FIG. 9 or 10.

At block 1635, the method 1600 may include transmitting DCI to the UE.In some examples, the DCI may be transmitted as part of the schedulinginformation transmitted at block 1630. In some examples, the method 1600may include indicating the presence of an uplink grant for the PUSCH inthe UpPTS in the DCI. The indication may be based at least in part on: astate of an information field included in the DCI, a masking of acontrol channel including the DCI with a predetermined CRC mask, anassociation of the uplink grant with a predetermined decoding candidate,a size of the DCI, an identifier of a subframe in which the DCI isreceived, a DCI format, or a combination thereof. The operations atblock 1635 may be performed using the wireless communication manager 920or 1020 described with reference to FIG. 9 or 10, the base stationwireless communication manager 1260 described with reference to FIG. 12,or the scheduling information transmission manager 945 or 1045 describedwith reference to FIG. 9 or 10.

At block 1640, the method 1600 may include managing HARQ. In someexamples, managing HARQ may include at least one of: separately managinguplink HARQ for the PUSCH in the UpPTS and uplink HARQ for PUSCHtransmissions in uplink TTIs, jointly managing the uplink HARQ for thePUSCH in the UpPTS and the uplink HARQ for PUSCH transmissions in uplinkTTIs, or transmitting the uplink HARQ for the PUSCH in the UpPTS and theuplink HARQ for PUSCH transmissions in uplink TTIs asynchronously. Theoperations at block 1640 may be performed using the wirelesscommunication manager 920 or 1020 described with reference to FIG. 9 or10, the base station wireless communication manager 1260 described withreference to FIG. 12, or the HARQ manager 1055 described with referenceto FIG. 10.

Techniques described herein may be used for various wirelesscommunications systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, andother systems. The terms “system” and “network” are often usedinterchangeably. A CDMA system may implement a radio technology such asCDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000covers IS-2000, IS-95, and IS-856 standards. IS-2000 Releases 0 and Amay be referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) may bereferred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRAincludes Wideband CDMA (WCDMA) and other variants of CDMA. A TDMA systemmay implement a radio technology such as Global System for MobileCommunications (GSM). An OFDMA system may implement a radio technologysuch as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11(Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM™, etc. UTRA andE-UTRA are part of Universal Mobile Telecommunication System (UMTS).3GPP LTE and LTE-A are new releases of UMTS that use E-UTRA. UTRA,E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from anorganization named 3GPP. CDMA2000 and UMB are described in documentsfrom an organization named “3rd Generation Partnership Project 2”(3GPP2). The techniques described herein may be used for the systems andradio technologies mentioned above as well as other systems and radiotechnologies, including cellular (e.g., LTE) communications over anunlicensed or shared bandwidth. The description above, however,describes an LTE/LTE-A system for purposes of example, and LTEterminology is used in much of the description above, although thetechniques are applicable beyond LTE/LTE-A applications.

The detailed description set forth above in connection with the appendeddrawings describes examples and does not represent all of the examplesthat may be implemented or that are within the scope of the claims. Theterms “example” and “exemplary,” when used in this description, mean“serving as an example, instance, or illustration,” and not “preferred”or “advantageous over other examples.” The detailed description includesspecific details for the purpose of providing an understanding of thedescribed techniques. These techniques, however, may be practicedwithout these specific details. In some instances, well-known structuresand apparatuses are shown in block diagram form in order to avoidobscuring the concepts of the described examples.

Information and signals may be represented using any of a variety ofdifferent technologies and techniques. For example, data, instructions,commands, information, signals, bits, symbols, and chips that may bereferenced throughout the above description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connectionwith the disclosure herein may be implemented or performed with ageneral-purpose processor, a digital signal processor (DSP), an ASIC, anFPGA or other programmable logic device, discrete gate or transistorlogic, discrete hardware components, or any combination thereof designedto perform the functions described herein. A general-purpose processormay be a microprocessor, but in the alternative, the processor may beany conventional processor, controller, microcontroller, or statemachine. A processor may also be implemented as a combination ofcomputing devices, e.g., a combination of a DSP and a microprocessor,multiple microprocessors, one or more microprocessors in conjunctionwith a DSP core, or any other such configuration.

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope and spirit of the disclosure and appended claims. For example,due to the nature of software, functions described above can beimplemented using software executed by a processor, hardware, firmware,hardwiring, or combinations of any of these. Features implementingfunctions may be physically located at various positions, includingbeing distributed such that portions of functions are implemented atdifferent physical locations. As used herein, including in the claims,the term “and/or,” when used in a list of two or more items, means thatany one of the listed items can be employed by itself, or anycombination of two or more of the listed items can be employed. Forexample, if a composition is described as containing components A, B,and/or C, the composition can contain A alone; B alone; C alone; A and Bin combination; A and C in combination; B and C in combination; or A, B,and C in combination. Also, as used herein, including in the claims,“or” as used in a list of items (for example, a list of items prefacedby a phrase such as “at least one of” or “one or more of”) indicates aninclusive list such that, for example, a phrase referring to “at leastone of” a list of items refers to any combination of those items,including single members. As an example, “at least one of: A, B, or C”is intended to cover A, B, C, A-B, A-C, B-C, and A-B-C., as well as anycombination with multiples of the same element (e.g., A-A A-A-A, A-A-B,A-A-C, A-B-B, A-C-C, B-B, B-B-B, B-B-C, C-C, and C-C-C or any otherordering of A, B, and C). As used herein, the phrase “based on” shallnot be construed as a reference to a closed set of conditions. Forexample, an exemplary step that is described as “based on condition A”may be based on both a condition A and a condition B without departingfrom the scope of the present disclosure. In other words, as usedherein, the phrase “based on” shall be construed in the same manner asthe phrase “based at least in part on.”

Computer-readable media includes both non-transitory computer storagemedia and communication media including any medium that facilitatestransfer of a computer program from one place to another. Anon-transitory storage medium may be any available medium that can beaccessed by a general purpose or special purpose computer. By way ofexample, and not limitation, non-transitory computer-readable media cancomprise RAM, ROM, electrically erasable programmable read only memory(EEPROM), compact disk (CD) ROM or other optical disk storage, magneticdisk storage or other magnetic storage devices, or any othernon-transitory medium that can be used to carry or store desired programcode means in the form of instructions or data structures and that canbe accessed by a general-purpose or special-purpose computer, or ageneral-purpose or special-purpose processor. Also, any connection isproperly termed a computer-readable medium. For example, if the softwareis transmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, DSL, orwireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,include CD, laser disc, optical disc, digital versatile disc (DVD),floppy disk and Blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

The previous description of the disclosure is provided to enable aperson skilled in the art to make or use the disclosure. Variousmodifications to the disclosure will be readily apparent to thoseskilled in the art, and the generic principles defined herein may beapplied to other variations without departing from the scope of thedisclosure. Thus, the disclosure is not to be limited to the examplesand designs described herein but is to be accorded the broadest scopeconsistent with the principles and novel techniques disclosed herein.

What is claimed is:
 1. A method for wireless communication at a userequipment (UE), comprising: identifying a physical uplink shared channel(PUSCH) to transmit in an uplink pilot time slot (UpPTS) of a subframe;determining a timing of a transmission time interval (TTI) for receivingscheduling information for the PUSCH, the timing of the TTI being basedat least in part on a capability of the UE; receiving, during the TTI,the scheduling information for the PUSCH to be transmitted in the UpPTS;and transmitting the PUSCH in the UpPTS based at least in part on thescheduling information.
 2. The method of claim 1, wherein the capabilityof the UE comprises a latency capability of the UE.
 3. The method ofclaim 2, wherein the latency reduction capability of the UE comprises atleast one of: a scheduling timing reduction capability, a TTI durationreduction capability, or a combination thereof.
 4. The method of claim3, further comprising: determining the UE is not capable of latencyreduction; and determining the timing of the TTI for receiving thescheduling information for the PUSCH based at least in part ondetermining that the UE is not capable of latency reduction, and whereinthe timing of the TTI comprises a leading boundary occurring at least3.5 subframes prior to the UpPTS.
 5. The method of claim 3, furthercomprising: determining that the capability of the UE comprises thescheduling time reduction capability; and determining the timing of theTTI for receiving the scheduling information for the PUSCH based atleast in part on determining that the capability of the UE comprises thescheduling time reduction capability, and wherein the timing of the TTIcomprises a leading boundary occurring at least two subframes prior tothe UpPTS.
 6. The method of claim 3, further comprising: determiningthat the capability of the UE comprises the TTI duration reductioncapability; and determining the timing of the TTI for receiving thescheduling information for the PUSCH based at least in part ondetermining that the capability of the UE comprises the TTI durationreduction capability, wherein the timing of the TTI comprises a leadingboundary occurring at least 2.5 subframes prior to the UpPTS.
 7. Themethod of claim 1, further comprising: separately managing uplink hybridautomatic repeat request (HARQ) for the PUSCH in the UpPTS and uplinkHARQ for PUSCH transmissions in one or more uplink TTIs.
 8. The methodof claim 1, further comprising: jointly managing uplink hybrid automaticrepeat request (HARQ) for the PUSCH in the UpPTS and uplink HARQ forPUSCH transmissions in one or more uplink TTIs.
 9. The method of claim1, further comprising: asynchronously receiving uplink hybrid automaticrepeat request (HARQ) for the PUSCH in the UpPTS and uplink HARQ forPUSCH transmissions in one or more uplink TTIs.
 10. The method of claim1, further comprising: receiving an acknowledgement of the PUSCH in theUpPTS in a same set of physical hybrid automatic repeat request (HARQ)indication channel (PHICH) resources used to acknowledge PUSCHtransmissions in one or more uplink subframes.
 11. The method of claim1, further comprising: receiving downlink control information (DCI); andidentifying an uplink grant for the PUSCH in the UpPTS, received in theDCI, based at least in part on: a state of an information field includedin the DCI, a masking of a control channel including the DCI with apredetermined cyclic redundancy check (CRC) mask, an association of theuplink grant with a predetermined decoding candidate, a size of the DCI,an identifier of a subframe in which the DCI is received, a DCI format,or a combination thereof.
 12. The method of claim 1, further comprising:receiving downlink control information (DCI); determining a size of theDCI; and identifying, within the DCI, at least one decoding candidatefor an uplink grant for the PUSCH in the UpPTS, the at least onedecoding candidate based at least in part on the size of the DCI. 13.The method of claim 1, further comprising: identifying a first powercontrol parameter for the TTI; and determining a second power controlparameter for the PUSCH in the UpPTS based at least in part on the firstpower control parameter for the TTI.
 14. The method of claim 13, whereinthe second power control parameter is determined based at least in parton: a semi-static relationship between the first power control parameterand the second control parameter, or a variable structure of the PUSCHin the UpPTS.
 15. A method for wireless communication comprising:determining whether to schedule a transmission of a physical uplinkshared channel (PUSCH) to be transmitted in an uplink pilot time slot(UpPTS) of a subframe; transmitting scheduling information to a userequipment (UE) based at least in part on a timing of a transmission timeinterval (TTI) for the PUSCH transmission in the UpPTS of a subframe,the timing of the TTI being based at least in part on a capability ofthe UE; transmitting, during the TTI, scheduling information for thePUSCH in the UpPTS; and receiving the PUSCH in the UpPTS based at leastin part on the scheduling information.
 16. The method of claim 15,wherein the capability of the UE comprises a latency capability of theUE.
 17. The method of claim 16, wherein the latency reduction capabilityof the UE comprises at least one of: a scheduling timing reductioncapability, a TTI duration reduction capability, or a combinationthereof.
 18. The method of claim 17, wherein the timing of the TTI fortransmitting the scheduling information for the PUSCH comprises at leastone of a leading boundary occurring at least 3.5 subframes prior to theUpPTS, a leading boundary occurring at least two subframes prior to theUpPTS, a leading boundary occurring at least 2.5 subframes prior to theUpPTS, or a combination thereof.
 19. The method of claim 15, furthercomprising: separately managing uplink hybrid automatic repeat request(HARQ) for the PUSCH in the UpPTS and uplink HARQ for PUSCHtransmissions in one or more uplink TTIs.
 20. The method of claim 15,further comprising: jointly managing uplink hybrid automatic repeatrequest (HARQ) for the PUSCH in the UpPTS and uplink HARQ for PUSCHtransmissions in one or more uplink TTIs.
 21. The method of claim 15,further comprising: asynchronously transmitting uplink hybrid automaticrepeat request (HARQ) for the PUSCH in the UpPTS and uplink HARQ forPUSCH transmissions in one or more uplink TTIs.
 22. The method of claim15, further comprising: transmitting an acknowledgement of the PUSCH inthe UpPTS in a same set of physical hybrid automatic repeat request(HARQ) indication channel (PHICH) resources used to acknowledge PUSCHtransmissions in one or more uplink subframes.
 23. The method of claim15, further comprising: transmitting downlink control information (DCI);and indicating a presence of an uplink grant for the PUSCH in the UpPTS,in the DCI, based at least in part on: a state of an information fieldincluded in the DCI, a masking of a control channel including the DCIwith a predetermined cyclic redundancy check (CRC) mask, an associationof the uplink grant with a predetermined decoding candidate, a size ofthe DCI, an identifier of a subframe in which the DCI is received, a DCIformat, or a combination thereof.
 24. The method of claim 15, furthercomprising: transmitting downlink control information (DCI), the DCIcomprising at least one decoding candidate for an uplink grant for thePUSCH in the UpPTS, the at least one decoding candidate based at leastin part on the size of the DCI.
 25. The method of claim 15, furthercomprising: receiving a random access preamble; and scheduling thetransmission of the PUSCH in the UpPTS in response to receiving therandom access preamble.
 26. An apparatus for wireless communication at auser equipment (UE), comprising: a processor; and memory in electroniccommunication with the processor; the processor and the memoryconfigured to: identify a physical uplink shared channel (PUSCH) totransmit in an uplink pilot time slot (UpPTS) of a subframe; determine atiming of a transmission time interval (TTI) for receiving schedulinginformation for the PUSCH, the timing of the TTI being based at least inpart on a capability of the UE; receive, during the TTI, the schedulinginformation for the PUSCH to be transmitted in the UpPTS; and transmitthe PUSCH in the UpPTS based at least in part on the schedulinginformation.
 27. The apparatus of claim 26, wherein the capability ofthe UE comprises a latency capability of the UE.
 28. The apparatus ofclaim 27, wherein the latency reduction capability of the UE comprisesat least one of: a scheduling timing reduction capability, a TTIduration reduction capability, or a combination thereof.
 29. Anapparatus for wireless communication at a network device, comprising: aprocessor; and memory in electronic communication with the processor;the processor and the memory configured to: determine whether toschedule a transmission of a physical uplink shared channel (PUSCH) tobe transmitted in an uplink pilot time slot (UpPTS) of a subframe;transmit scheduling information to a user equipment (UE) based at leastin part on a timing of a transmission time interval (TTI) for the PUSCHtransmission in the UpPTS of a subframe, the timing of the TTI beingbased at least in part on a capability of the UE; transmit, during theTTI, scheduling information for the PUSCH in the UpPTS; and receive thePUSCH in the UpPTS based at least in part on the scheduling information.30. The apparatus of claim 29, wherein the capability of the UEcomprises a latency capability of the UE.